Bug #230
closed
Run functionality doesn't work in daemon mode
Added by SyRenity Now about 14 years ago.
Updated about 14 years ago.
Category:
Puppet integration
|
|
Description
- Launched Foreman via init.d script
- Got immediately error notice
- Suspect permissions (i.e. foreman running under foreman account)
- Status changed from New to Need more information
- Priority changed from High to Normal
is this a puppet bug? or permission issue on the sudo side? do you have any more information about this problem?
This seems to be issue present only when Foreman runs under daemon.
When I su to foreman account, then launch the following command:
sudo /usr/sbin/puppetrun --host usdemo.test.com
It works normally.
By the way, there is nothing in logs -i.e. the cmd variable doesn't contain anything (whether 0 or any error code).
Just empty string.
do you have:
Defaults:foreman !requiretty
in your sudoers file?
- Status changed from Need more information to Closed
SyRenity Now wrote:
That worked!
Please update the wiki for Puppetrun, as it contains only these instructions:
foreman ALL = NOPASSWD: /usr/sbin/puppetrun
http://theforeman.org/projects/foreman/wiki/Puppetrun
You have wiki access too :)
it was documented in the puppet module for foreman :)
Also available in: Atom
PDF
Updated by 
Updated by