Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-4361

puppet_agent module does not restart puppet and pxp-agent services after upgrade on Solaris

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: puppet_agent 1.3.1
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Template:
      MODULES Bug Template
    • Team:
      Platform OS
    • Method Found:
      Customer Feedback
    • CS Priority:
      Normal
    • CS Frequency:
      2 - 5-25% of Customers
    • CS Severity:
      3 - Serious
    • CS Business Value:
      3 - $$$$
    • CS Impact:
      Hide
      This will impact all customers that have puppet agents on Solaris 10 or 11 nodes who are using the puppet_agent module to upgrade their nodes. They will all have to work around this via a shell script or some other means. While this issue has been fixed in the Puppet 5 agent these users won't be able to get their without using a workaround at least once.

      We should really put a fix into the module for this, or at the very least publish a known issue which includes a shell script to resolve this.
      Show
      This will impact all customers that have puppet agents on Solaris 10 or 11 nodes who are using the puppet_agent module to upgrade their nodes. They will all have to work around this via a shell script or some other means. While this issue has been fixed in the Puppet 5 agent these users won't be able to get their without using a workaround at least once. We should really put a fix into the module for this, or at the very least publish a known issue which includes a shell script to resolve this.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Using puppetlabs-puppet_agent 1.3.1 to upgrade a Solaris 11 i86pc 2016.2.1 system to 2016.4.2. The upgrade is successful, but the old versions of the services are left running. Only mcollective is restarted on a subsequent Puppet run.

      Results:

      # /opt/puppetlabs/bin/puppet --version
      4.5.3
      # ps -ef |grep puppet
          root  2664  2198   0 09:49:29 pts/1       0:00 grep puppet
          root  2604     1   0 09:49:09 ?           0:00 /opt/puppetlabs/puppet/bin/pxp-agent
          root  2370     1   0 09:46:13 ?           0:09 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/bin/puppet agent
          root  2626     1   0 09:49:11 ?           0:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived --pid=/
      # /opt/puppetlabs/bin/puppet agent -t
      <snip>
      Notice: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: ensure changed '1.5.3,5.11-1:20160720T002950Z' to '1.7.1,5.11-1:20161012T032706Z'
      Notice: Applied catalog in 73.10 seconds
      # ps -ef |grep puppet
          root  2950  2198   0 09:55:10 pts/1       0:00 grep puppet
          root  2604     1   0 09:49:09 ?           0:00 /opt/puppetlabs/puppet/bin/pxp-agent
          root  2370     1   0 09:46:13 ?           0:09 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/bin/puppet agent
          root  2626     1   0 09:49:11 ?           0:01 /opt/puppetlabs/puppet/bin/ruby /opt/puppetlabs/puppet/bin/mcollectived --pid=/
      # /opt/puppetlabs/bin/puppet --version
      4.7.0
      

      Note that the ps output shows the same pids for the pxp-agent and puppet daemons before and after the upgrade.

      Expected results: The upgrade should restart the services to get the upgraded code loaded as the currently running service.

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  adam.bottchen Adam Bottchen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    Zendesk Support