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: If user sets a Satellite URL at installation time, the installation environment will be provisioned to communicate with the given Satellite instance instead of the Red Hat hosted subscription infrastructure.
If the user then decides to unregister, Anaconda rolls the "Satellite provisioning" back so that it is easily possible to try registering again to Red Hat hosted subscription infrastructure or a different Satellite instance.
Unfortunately this rollback does not happen if the registration process fails for some reason (such as for example wrong password) and the installation environment will remain provisioned for the given Satellite instance.
Version-Release number of selected component (if applicable):
How reproducible:
anaconda-33.16.6.1-1
Steps to Reproduce:
1. attempt to register to a Satellite instance from Anaconda with wrong password
Actual results:
Registration fails, Anaconda reports error & system remains provisioned for Satellite.
Easy way to check for this is to open /etc/rhsm/rhsm.conf and check the "prefix" key in the "[server]" section. If you see "prefix = /rhsm" then the system is provisioned for Satellite.
Expected results:
Registration fails, Anaconda reports error & Satellite provisioning is rolled back.
Easy way to check for this is to open /etc/rhsm/rhsm.conf and check the "prefix" key in the "[server]" section. If you see "prefix = /subscription" then the system is pointing to the Red Hat subscription infrastructure.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: anaconda), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:2326