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

On EL4, the AIO puppet-agent is unable to manage the puppet service

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.2.3
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      2
    • Sprint:
      RE 2015-09-23
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      puppet-agent installs a puppet service, and trying to use puppet to manage the service on EL4 only, e.g. ensure=>running, would result in the service being killed

      Description

      On EL4 builds of the AIO puppet-agent, Puppet is unable to manage the puppet service:

      As seen in the puppet-agent 1.2.4 build for EL4:

      # /opt/puppetlabs/puppet/bin/puppet resource service puppet ensure=running
      service { 'puppet':
        ensure => 'running',
      }
      # service puppet status
      puppet is stopped
      # service puppet start
      Starting puppet agent:                                     [  OK  ]
      # /opt/puppetlabs/puppet/bin/puppet resource service puppet ensure=stopped
      Error: /Service[puppet]/ensure: change from running to stopped failed: SIGTERM
      Error: Could not run: SIGTERM
      

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  qa qa
                  Reporter:
                  geoff.nichols Geoff Nichols
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: