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

puppet_agent: Downgrades puppet agent version on MoM

    XMLWordPrintable

    Details

    • Template:
      MODULES Bug Template
    • Acceptance Criteria:
      Hide

      Documentation that shows the customer that this should be removed from classification on the MoM during an upgrade or the puppet_agent module should not manage the MoM's agent version.

      Show
      Documentation that shows the customer that this should be removed from classification on the MoM during an upgrade or the puppet_agent module should not manage the MoM's agent version.
    • Team:
      Platform OS
    • Method Found:
      Customer Feedback

      Description

      Basic Info
      Module Version: 1.3.1
      Puppet Version: 2016.4.6
      OS Name/Version: RHEL7

      Describe your issue in as much detail as possible
      When a customer does a PE upgrade and has the MoM classified with puppet_agent and an older version of the puppet agent, the agent on the MoM may get downgraded. This will likely break the PE installation.

      Desired Behavior:
      The puppet_agent module should not manage the puppet version on the MoM. Or we should document that it should be disabled as a part of the upgrade.

      Actual Behavior:
      puppet_agent downgraded the puppet agent version on the MoM from 1.10.4 to 1.7.1.

      puppet-agent[42625]: (/Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure) ensure changed '1.10.4-1.el7' to '1.7.1-1.el7'
      

      Solution

      No longer manage the puppet-agent version on PE infrastructure nodes (master, console, puppetdb, compile master, amq hub/spoke, etc...).

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jarret.lavallee Jarret Lavallee
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support