[PUP-10484] Unregistered yum subscription-manager confuses yum package provider - Puppet Jira Server

XML

Word

Printable

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.

Console Browser:
Chrome
Master Config:
Monolithic
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

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:

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

relates to

PUP-10432 RedHat RHBA-2020:1028 breaks yum.rb in yum provider for some systems