Jira (PUP-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist

[Erik Hansen (JIRA)]

Title: Message Title

Erik Hansen created an issue   Puppet / PUP-6822 Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist Issue Type: Bug Assignee: Unassigned Created: 2016/10/16 9:36 AM Priority: Normal Reporter: Erik Hansen Linux agents don't seem to have this issue, for example: ]# puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}' Notice: Compiled catalog for pe-201620-master.example.com in environment production in 0.12 seconds Notice: Applied catalog in 0.33 seconds However, on Windows, an attempt to apply the same resource gives: PS C:\Users\Administrator> puppet apply -e 'service {"notaservice": ensure => "stopped", enable => false,}' Notice: Compiled catalog for windows-agent1 in environment production in 0.03 seconds Error: /Stage[main]/Main/Service[notaservice]: Could not evaluate: Cannot get status of notaservice, error was: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service. Wrapped exception: The specified service does not exist as an installed service. - OpenService: The specified service does not exist as an installed service. Notice: Applied catalog in 0.14 seconds Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.