Issue #16910 has been reported by Deven Phillips. ---------------------------------------- Bug #16910: "service" type's "status" parameter not working since upgrade to 3.0.0 https://projects.puppetlabs.com/issues/16910
Author: Deven Phillips Status: Unreviewed Priority: Normal Assignee: Category: service Target version: 3.0.x Affected Puppet version: 3.0.0 Keywords: puppet service status hasstatus Branch: We have a number of applications written in Erlang for our business. These applications are started from non-standard init scripts on a Debian platform. The init script/service names do not match the process names, so we have been using the "status" and "hasstatus" parameters for the "service" type to specify how to test the application state. The standard way to test our Erlang application state is to call: /etc/init.d/servicename ping | /bin/grep pong The grep command would then return a 0 exit code if the service is responding properly. This was working properly until our update to 3.0.0, but now it is not working properly and as such the service is being restarted on every puppet run. I modified our manifests to instead specify a custom pattern and set hasstatus=false, and this approach IS working in the latest version. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
