Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6489

Windows service resource doesn't understand trigger start services

    Details

    • Template:
    • Team:
      Platform OS

      Description

      Windows services can be configured as trigger start, which means while the service is started, it may not always be running at the time that Puppet looks at it. When using a manifest with enable => 'true', ensure => 'running', this may mean Puppet is constantly turning the service back on, even though it probably shouldn't. Changing ensure to scheduled would likely be very difficult to manage right now... so uncertain yet what the best approach would be:

      The docs for Service trigger events are at https://msdn.microsoft.com/en-us/library/windows/desktop/dd405513(v=vs.85).aspx

      The code that deals with Windows service types is at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/windows.rb#L46-L54

      The gem we're using does have the constants available associated with trigger starts:
      https://github.com/djberg96/win32-service/blob/ffi/lib/win32/windows/constants.rb#L88

      This was discovered while looking at the MODULES-2420 and the Windows wuaserv

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ethan Ethan Brown
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Zendesk Support