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

puppet_agent fails to upgrade from 2016.2.0 to 2016.2.1 on Solaris 10

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • puppet_agent 1.5.0
    • puppet_agent
    • None
    • Normal
    • 2 - 5-25% of Customers
    • 3 - Serious
    • 3 - $$$$
    • 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.
    • Bug Fix
    • An issue preventing upgrades on Solaris 10 - where the Puppet service would be killed before the upgrade completed - has been addressed. Upgrades will now happen after the Puppet run has completed on Solaris 10.

    Description

      Re-create steps:

      1. Start with a 2016.2.0 agent pointed to a 2016.2.1 master.
      2. Add a puppet_agent definition to site.pp for the agent:

      node /cd9qmm656puqio9.delivery.puppetlabs.net/ {
      		 
        class {'::puppet_agent':
      		 
            package_version => '1.5.3',
      		 
        }
      		 
      }

      3. Wait for the Solaris 10 agent to check in.

      Results:

      The upgrade will fail. The logs show the Puppet agent getting a SIGTERM right after trying to run `/usr/sbin/pkgrm -a /opt/puppetlabs/packages/solaris-noask -n puppet-agent`.

      Aug 24 13:21:36 solaris-10-64.delivery.puppetlabs.net puppet-agent[1757]: [ID 702911 daemon.notice] Starting Puppet client version 4.5.2
      		 
      Aug 24 13:21:40 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.notice] (/Stage[main]/Puppet_agent::Prepare::Package/File[/opt/puppetlabs/packages]/ensure) created
      		 
      Aug 24 13:21:42 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.notice] (/Stage[main]/Puppet_agent::Prepare::Package/File[/opt/puppetlabs/packages/puppet-agent-1.5.3-1.i386.pkg.gz]/ensure) defined content as '{md5}f8a70a105c693e136f2b119c6d587fdf'
      		 
      Aug 24 13:21:43 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.notice] (/Stage[main]/Puppet_agent::Osfamily::Solaris/Exec[unzip puppet-agent-1.5.3-1.i386.pkg.gz]/returns) executed successfully
      		 
      Aug 24 13:21:43 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.notice] (/Stage[main]/Puppet_agent::Osfamily::Solaris/File[/opt/puppetlabs/packages/solaris-noask]/ensure) defined content as '{md5}2fa0d730f040d9d3f9bface697aeb042'
      		 
      Aug 24 13:21:44 solaris-10-64.delivery.puppetlabs.net puppet-agent[1757]: [ID 702911 daemon.notice] Caught TERM; exiting
      		 
      Aug 24 13:21:44 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.error] Execution of '/usr/sbin/pkgrm -a /opt/puppetlabs/packages/solaris-noask -n puppet-agent' returned :
      		 
      Aug 24 13:21:44 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.error] (/Package[puppet-agent]/ensure) change from 1.5.2-1 to absent failed: Execution of '/usr/sbin/pkgrm -a /opt/puppetlabs/packages/solaris-noask -n puppet-agent' returned :
      		 
      Aug 24 13:21:44 solaris-10-64.delivery.puppetlabs.net puppet-agent[1758]: [ID 702911 daemon.notice] Caught TERM; exiting

      Expected Results:

      The puppet_agent module should upgrade Solaris 10 agents as it does CentOS agent installs.

      Attachments

        Issue Links

          is supported by

          Bug - A problem which impairs or prevents the functions of the product. PUP-7110 Unable to halt Puppet service on Solaris using Puppet

          • Major - Major loss of function.
          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              adam.bottchen Adam Bottchen
              adam.bottchen Adam Bottchen
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support