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:
This is definitely a race condition, as I have seen this happen & not happen in two subsequent runs on the same VM, the same custom generated boot ISO with Aanconda RHSM integration code & the same kickstart.
I am setting a custom rhsm baseurl pointing to the stating CDN. In one case, the URL got applied as expected in the resulting redhat.repo file after calling AutoAttach() in the other case, redhat.repo was still pointing to the default non-staging CDN URL.
Version-Release number of selected component (if applicable):
1.26.5
How reproducible:
Race condition.
Steps to Reproduce:
1. set custom rhsm baseurl via the DBus API
2. register
3. call AutoAttach()
4. See /etc/yum.repos.d/redhat.repo and check if you custom baseurl has been used or ignored.
Actual results:
If you win the race, the custom rhsm baseurl will be ignored.
Expected results:
The rhsm baseurl is set atomically and always reflected in all subsequent calls of the RHSM API.
Additional info:
Once you win the race, even a restart or the rhsm systemd service will not fix the already generated redhat.repo file. But, calling "subscription-manager repos", a read only CLI call the list available repositories, will not only list repos with the correct (custom) baseurl, it will repair *fix the existing redhat.repo file in place*.
Comment 7RHEL Program Management
2021-05-26 07:30:49 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.