puppetlabs / puppetlabs/puppetlabs-apache

Error Executing Exec Commands in puppetlabs-apache Module

Open
#2,570 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the Bug

I encountered an error while trying to apply the puppetlabs-apache module (version 12.1.0) on my agent. The error message indicates that an Exec command is being defined as an Array instead of a String.

Expected Behavior

I expected the Puppet agent to successfully install Apache without any errors during the execution of the puppet agent -t command.

Steps to Reproduce

Steps to reproduce the behavior:
Install the Puppet agent on the target node.
Install the puppetlabs-apache module (version 12.1.0).
Create a simple manifest for installing Apache.
Run the Puppet agent with the command puppet agent -t.

Environment

Version: puppetlabs-apache 12.1.0
Platform: Ubuntu 22.04

Additional Context

The error message received is:
Error: Failed to apply catalog: Parameter command failed on Exec[mkdir /etc/apache2/conf.d]: Command must be a String, got value of class Array (file: /etc/puppetlabs/code/environments/production/modules/apache/manifests/init.pp, line: 603)

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 at manifests/init.pp around line 603 and reproduce the catalog application with puppetlabs-apache 12.1.0 on Ubuntu 22.04 using puppet agent -t. Investigate why Exec[mkdir /etc/apache2/conf.d] receives an Array for its command; done means Apache installs successfully without the catalog application error.

Written by the indexing model from the issue text.

Assessment

Tech stack
apache
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.