Issue #8592 has been updated by Nigel Kersten. Priority changed from Normal to Low
I'm not sure we have correct defined behavior here. Given the service ensure property doesn't cover actual existence, I'm quite sure we have different behaviors on different platforms and service providers. For example, the launchd provider definitely fails in this situation: <pre> $ puppet resource service foobar Could not run: Unable to find launchd plist for job: foobar </pre> but I think the init.d providers have all behaved like this for a while. It would be good to bring some consistent semantics to all the service providers. ---------------------------------------- Bug #8592: Non-existent service succeeds with hasstatus=true on RHEL based OSes https://projects.puppetlabs.com/issues/8592 Author: Dominic Maraglia Status: Investigating Priority: Low Assignee: Category: service Target version: Affected Puppet version: 2.6.4 Keywords: Branch: Running "puppet resource service foo hasstatus=true" on RHEL derived OSes succeeds. Correct behaviour is to fail indicating and invalid service. <pre> [root@rhel50-x86-64 init.d]# puppet resource service pe-puppet hasstatus=true service { 'pe-puppet': ensure => 'stopped' } </pre> <pre> [root@centos-55-64-1 ~]# puppet resource service foo hasstatus=true service { 'foo': ensure => 'stopped' } </pre> -- 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.
