Foreman triggered Puppet run / no refresh of service

asked 2015-05-31 15:35:20 -0600

23r0 gravatar image


I'm facing a strange problem with a foreman (v. 1.7.0) / puppet (v. 3.2.4) setup. Whenever a puppet run is started via cli (puppet agent -tv) or cron, everything is fine, the problematic module works like a charm and a 'refresh' to the service will be issued. But: When I start the puppet run via forman there will be no 'refresh' issued, but "ensure changed 'stopped' to 'running'". The module in this case is JBOSS, but actually I don't think that it does matter. The command that foreman is issuing is "mco puppet runonce". Why does puppet behave differently when started via cron/cli or via Foreman? Any hints welcome.



edit retag flag offensive close merge delete