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

acceptance: service stop/start/status should work correctly in single run

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-06-10

      Description

      might be covered by:
      tests/ticket_7165_no_refresh_after_starting_service.rb

      if not, add it, it's almost certainly a few line change.

      find some service that most VMs have: unix/windows, and do something like:

      service { '#{service}':
        ensure => stopped
       } ~> 
      service { '#{service}':
        ensure => started
       } 
      

      the ensure calls status, but i guess we could test with and without status binary being specified? (real resource and a fake one)

      it doesn't make sense to declare these two identical services.
      perhaps subscribe the service to a file, touch the file and ensure the service restarts?

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              erict Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support