Issue #8592 has been updated by Peter Meier. Priority changed from High to Normal
> I dont care if `foo` is installed or not, I just don't want that service > `foo` is running. I think it whould be a bad idea to raise an error in case > there is no such service `foo`. And in my opinion `puppet resource` should > behave the same. + 1, how should it fail if the service is not present? Catalog fail would make it very hard to remove/disable services. ---------------------------------------- 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: Normal 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.
