Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Upon a new subscribe of a pool, the redhat.repo file isn't populated for some random amount of time (sometimes 10-15 minutes) after subscribing. For that time period, no repos are available. `yum clean all` and `service rhsmcertd restart` do not help in this case.
Version-Release number of selected component (if applicable):
[root@jmolet-testday product]# rpm -qa | egrep "redhat-release|subscription-manager|python-rhsm"
redhat-release-workstation-6Workstation-6.1.0.1.el6.x86_64
subscription-manager-firstboot-0.95.4-1.el6.x86_64
python-rhsm-0.95.4-1.el6.noarch
subscription-manager-gnome-0.95.4-1.el6.x86_64
subscription-manager-0.95.4-1.el6.x86_64
How reproducible:
Randomly. I can consistently reproduce it on one vm, but can't on another clone of that vm using the same pools/users.
Steps to Reproduce:
1. subscription-manager register
2. subscription-manager subscribe --pool=<some pool with a content set>
3. yum repolist all
Actual results:
No new repos are listed
Expected results:
The repos/content sets from the subscription are populated immediately
Terminal Log of reproduction:
(see attached)
Note that for the attachment above in comment 1, that I waited about 10 minutes between the last two commands:
cat /etc/yum.repos.d/redhat.repo (showing an empty repo file), the yum repolist all command at the end.