Bug #230
closedRun functionality doesn't work in daemon mode
Description
- Launched Foreman via init.d script
- Clicked Run on some node
- Got immediately error notice
- Nothing in logs
- Suspect permissions (i.e. foreman running under foreman account)
Updated by Ohad Levy almost 15 years ago
- 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?
Updated by SyRenity Now almost 15 years ago
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.
Updated by SyRenity Now almost 15 years ago
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.
Updated by Ohad Levy almost 15 years ago
do you have:
Defaults:foreman !requiretty
in your sudoers file?
Updated by SyRenity Now almost 15 years ago
That worked!
Please update the wiki for Puppetrun, as it contains only these instructions:
foreman ALL = NOPASSWD: /usr/sbin/puppetrun
Updated by Ohad Levy almost 15 years ago
- 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
You have wiki access too :)
it was documented in the puppet module for foreman :)