Skip to content

Parameter command failed on Exec[/usr/bin/systemctl daemon-reload] #1097

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
yoshz opened this issue Dec 6, 2022 · 2 comments
Open

Parameter command failed on Exec[/usr/bin/systemctl daemon-reload] #1097

yoshz opened this issue Dec 6, 2022 · 2 comments
Assignees

Comments

@yoshz
Copy link

yoshz commented Dec 6, 2022

Describe the Bug

Just upgraded to 4.0.0 and noticed this error:
Parameter command failed on Exec[/usr/bin/systemctl daemon-reload]

Seems to be introduced by this commit: dd2cc1e

I am running Puppet 6 and that doesn't support an array as command.

Environment

  • Version 4.0.0
  • Platform CentOS 7
  • Puppet 6
LukasAud added a commit that referenced this issue Dec 6, 2022
Prior to this commit, due to a mistake, there was a reversion to the
previously implemented bump to minimum required puppet version, which
was part of the CVE update.

This commit aims to address issue 1097 in Github which brings to light
the need for this puppet bump to be restored to 6.24
@LukasAud
Copy link
Contributor

LukasAud commented Dec 6, 2022

Hi @yoshz, thanks for bringing this to our attention. It seems a mistake was made by reverting the version bump and the module does indeed require a minimum puppet version of 6.24.0 to work properly. We are addressing this issue here and a new release should be in the forge soon.

jordanbreen28 pushed a commit that referenced this issue Dec 6, 2022
Prior to this commit, due to a mistake, there was a reversion to the
previously implemented bump to minimum required puppet version, which
was part of the CVE update.

This commit aims to address issue 1097 in Github which brings to light
the need for this puppet bump to be restored to 6.24
@LukasAud LukasAud added the bugfix label Dec 7, 2022
@LukasAud LukasAud self-assigned this Dec 7, 2022
@greatflyingsteve
Copy link
Contributor

greatflyingsteve commented May 10, 2023

I am getting a PR prepared which addresses this issue. The exec in question hasn't been required since at least Puppet 6.11.1 (see PUP-10149), so there is no reason it should have been changed instead of simply removed when the format was converted from command-as-string to command-as-array. My environment is (for another few weeks) running Puppet 6.19 on CentOS 7, and this is literally the only thing that was broken for me on pre-6.24 Puppet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants