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

puppet_agent : newer versions of gpg2 change output format, causing attempts to get gpg keyid to fail

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: puppet_agent
    • Labels:
    • Environment:

      sles 15

    • Template:
      MODULES Bug Template
    • Team:
      Platform OS
    • Sprint:
      Platform OS Kanban
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      Basic Info
      Module Version: 2.0.1
      Puppet Version: 5.5.8
      OS Name/Version: sles 15

      While testing out sles15 support in pe2018.1.5 I use the puppet_agent module to ensure the agent version is 5.5.8. The exec which installs the gpg keys has an unless attribute that is trying to obtain the keyid, but fails due to gpg2.2 having a different output format than the code expected. So this '| cut --characters=11-18' no longer retrieves the keyid when using gpg2.2

      Desired Behavior: expected gpg keys to be imported only once
      gpg 2.0 output on sles12sp3:
      gpg --homedir /root/.gnupg --throw-keyids < /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
      pub 4096R/4BD6EC30 2010-07-10 [expires: 2017-01-05]

      Actual Behavior: keys continue to re-import in every puppet run

      gpg2 2.2 output on sles15:
      gpg --homedir /root/.gnupg --throw-keyids < /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
      gpg: WARNING: no command supplied. Trying to guess what you mean ...
      pub rsa4096 2010-07-10 [SC] [expired: 2017-01-05]
      47B320EB4C7C375AA9DAE1A01054B7A2*4BD6EC30*
      uid Puppet Labs Release Key (Puppet Labs Release Key) <info@puppetlabs.com>

        Attachments

          Activity

            People

            Assignee:
            scott.garman Scott Garman
            Reporter:
            jaketrogers Jake Rogers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support