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

Unregistered yum subscription-manager confuses yum package provider

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: PUP 6.14.0
    • Fix Version/s: PUP 6.15.0
    • Component/s: Types and Providers
    • Labels:
      None
    • Environment:

      Somehow the subscription-manager.conf appeared in my system as I was setting up docker and docker-compose. It was not until later that I realized it broke puppet's package provider.

    • Template:
    • Console Browser:
      Chrome
    • Master Config:
      Monolithic
    • Agent OS:
      CentOS 7
    • Master OS:
      CentOS 7
    • Acceptance Criteria:
      Hide

      Even if this setting & warning is in place, it shouldn't confuse the package provider to the point that it becomes inoperative.

      Show
      Even if this setting & warning is in place, it shouldn't confuse the package provider to the point that it becomes inoperative.
    • Team:
      Platform OS
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      If the yum subscription-manager is enabled but not registered with an entitlement server, a warning will show in every output of the yum command:

       

      This system is not registered with an entitlement server. You can use subscription-manager to register. 
      

      This confuses the yum package provider, causing Package resources to no longer be able to update packages.

      Steps to repro:

      1. Install CentOS 7
      2. Create /etc/yum/pluginconf.d/subscription-manager.conf
      3. Set contents of the above .conf file to:
        [main]
        enabled=1
      4. Run yum check-update and notice the warning
      5. Now try to update a yum package using puppet:
        puppet resource package <name> ensure=latest
      6. You'll notice the package doesn't get updated
      7. Go back to the .conf file and set enabled=0
      8. Retry updating the yum package using puppet and notice it now works.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              kevin.reeuwijk Kevin Reeuwijk
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support