Jira (PUP-1277) service does not implement custom start / stop commands on windows

[Mark (JIRA)]

Title: Message Title

Mark commented on PUP-1277   Re: service does not implement custom start / stop commands on windows It seems it still uses the default 'net stop/start [service]' and doesn't take into account what you set with 'stop' or 'start'. One of my services doesn't actually stop with 'net stop [service]', it takes a little longer. Here's an example: When I do 'net stop gitlab-runner', it throws a message after a couple of seconds: "The gitlab-runner service could not be stopped". It then actually takes another couple of seconds for the service to actually stop, but meanwhile Puppet is trying to start it again already, which results in: "The service is starting or stopping. Please try again later.". It then takes until the next Puppet run to actually start the service again. However, when I use Powershell to stop the service, it actually waits until the service is entirely stopped, using 'Stop-Service gitlab-runner'. Looks like this in Puppet DSL: stop => 'c:\windows\system32\windowspowershell\v1.0\powershell.exe Stop-Service gitlab-runner', However that does nothing. The output of the Puppet run actually says it's using 'net stop' still. And that is correct, according to the code in '/lib/puppet/provider/service/windows.rb', it doesn't take start/stop parameters into account, it always uses 'net': net(:start, @resource[:name]) net(:stop, @resource[:name]) The 'restart' parameter isn't used at all either. 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.