Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-5309

Yum package provider: ensure => latest fails when kernel is updated but not current

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • PUP 4.2.2
    • PUP 4.3.0
    • None
    • None
    • PE 2015.2.1, RHEL 7.0

    • 1
    • Client 2015-11-11
    • Bug Fix
    • The yum provider will no longer throw "undefined method `[]' for nil:NilClass" if the yum-security plugin is enabled when trying to manage a yum package.

    Description

      Similar to PUP-4497, puppet fail to run when there are kernel upgrade that didnt get apply:

      # yum check-update 
      Loaded plugins: product-id, rhnplugin, subscription-manager 
      This system is receiving updates from RHN Classic or Red Hat Satellite.
       
      openldap.x86_64 2.4.39-7.el7_1 rhel-x86_64-server-7 
      Security: kernel-3.10.0-229.14.1.el7.x86_64 is an installed security update 
      Security: kernel-3.10.0-123.el7.x86_64 is the currently running version
      

      Error:

      Error: /Stage[main]/Pe_r10k::Package/Package[pe-r10k]/ensure: change from 2.0.3.0-1.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass 
      Error: Could not get latest version: undefined method `[]' for nil:NilClass 
      Error: /Stage[main]/Puppet_enterprise::Packages/Package[pe-java]/ensure: change from 1.8.0.51-1.b16.pe.el7 to latest failed: Could not get latest version: undefined method `[]' for nil:NilClass 
      Error: Could not get latest version: undefined method `[]' for nil:NilClass 
      

      When system is rebooted to use the latest kernel, the error will go away.

      Attachments

        Issue Links

          Activity

            People

              erict Eric Thompson
              joshua.tee Joshuatly Tee
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support