-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
sysctl gives returned error 255 first time #53
Comments
Just tested with version 0.7.0 and it works fine, perhaps to be related with;
|
@sheijmans do you mean it's broken on the current version, but working on an older one? |
@domcleal yes it is broken in the current version (v1.0.0) for the above manifest, it works in v0.7.0. |
Thanks for confirming. Which OS is this? |
This was on RHEL64, I will also check it on RHEL59. |
On RHEL59 it also works with v0.7.0 and with v1.0.0 the same message as on RHEL64 but the second time you run it, it doesn't work as it does on RHEL64. |
I'm running into this same issue on ubuntu 12.04 with v1.0.0. It does not clear itself up. |
|
Ah, this works in a shell because the shell will parse the quotes and remove them when executing the command. In Puppet, it's running the command directly and passing the quotes straight into the arguments. |
Ok, I'll make a PR for this as it's affecting me right now :) give me a few minutes! |
+1 |
+1 One workaround I've found is setting exec { 'reload sysctl':
command => 'sysctl -p',
refreshonly => true,
path => '/sbin/:/usr/sbin/:/usr/bin/:/bin/',
} |
+1 |
Thanks for all the reports, and to @kitchen for fixing the bug. Sorry it took me ages to release. I've just put out v1.0.1, but hit an error uploading to the Forge, so in the meantime, grab it from GitHub releases here: https://github.com/hercules-team/augeasproviders/releases/tag/v1.0.1 |
Hi,
when using sysctl in a manifest, the first time it returns an error 255, why does this happen?
Regards,
Stefan
The text was updated successfully, but these errors were encountered: