Uploaded image for project: 'Community Package Repository (Archived, moved to puppet.atlassian.net)'
  1. Community Package Repository (Archived, moved to puppet.atlassian.net)
  2. CPR-382

Update to puppet-agent-1.7.0-1.el7 could be handled better

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Incomplete
    • None
    • 2017/08/02
    • Packaging
    • None

    Description

      The update to puppet-agent-1.7.0-1.el7 failed because it was trying to update without the new release key having already been installed:

      $ sudo yum update
      <snip>
      puppet-agent x86_64 1.7.0-1.el7 puppetlabs-pc1 24 M
      puppetlabs-release noarch 22.0-2 puppetlabs-products 14 k
      puppetlabs-release-pc1 noarch 1.1.0-2.el7 puppetlabs-pc1 14 k
      <snip>
      Is this ok [y/d/N]: y
      Downloading packages:
      warning: /var/cache/yum/x86_64/7/puppetlabs-pc1/packages/puppet-agent-1.7.0-1.el7.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID ef8d349f: NOKEY
      Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs-PC1

      The GPG keys listed for the "Puppet Labs PC1 Repository el 7 - x86_64" repository are already installed but they are not correct for this package.
      Check that the correct key URLs are configured for this repository.

      Failing package is: puppet-agent-1.7.0-1.el7.x86_64
      GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs-PC1

      If I broke this down and updated the two release packages first, then the agent later, all was well and flowed smoothly. To me this would suggest that puppet-agent is missing a versioned dependency on one of those two newer release packages. With that in place, yum would just do the right thing automatically.

      Attachments

        Activity

          People

            ryan.mckern Ryan McKern
            jflorian John Florian
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Zendesk Support