puppetlabs / puppetlabs/puppetlabs-apache

apache::mod::fastcgi is needed by apache::fastcgi::server but is not present.

Open Beginner friendly
#2,640 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bugfix
Dominant language
Puppet
Stars
356
Forks
1.1k
Avg merge
3m
Merged PRs (30d)
1

Description

Describe the Bug

apache::mod::fastcgi doesn't exist, but apache::fastcgi::server imports it.

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Could not find class ::apache::mod::fastcgi for hostname.com (file: /etc/puppetlabs/code/environments/apache/external/apache/manifests/fastcgi/server.pp, line: 43, column: 3) (file: /etc/puppetlabs/code/environments/apache/modules/ourapache/manifests/file.pp, line: 254) on node reli.cs.umbc.edu
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Expected Behavior

apache::mod::fastgi should be importable, or apache::fastcgi::server should not be present.

Steps to Reproduce

Declare any apache::fastcgi::server resource.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apache/manifests/fastcgi/server.pp around line 43 and inspect how apache::fastcgi::server imports apache::mod::fastcgi. Reproduce the issue by declaring apache::fastcgi::server, then check the module's existing class definitions and relevant tests. Done means the resource can be declared without the missing-class catalog error, or the unsupported resource is removed consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
apache
Domain
backend, infrastructure
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
66/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.