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.

It has been agreed with the RHSM team to stop explicitly issuing auto-attach calls in Simple Content access mode in RHEL 8.7 & RHEL 9.1.

Thankfully, this also coincides with the enable_content property being added to the Register() method used for username+password registration, which will make RHSM do the needed steps transparently from the client (eq. Anaconda) point of view. [0]

There is no such property for the RegisterWithActivationKeys(), but this can be handled by enabling auto-attach for the key being used. Attempting to use a key without auto-attach being enabled for it is not expected to work for the installation, so dropping the auto attach call for org + key authentication should not be a problem.

To summarize, the plan is to:

1) stop calling auto-attach
2) for username+password auth use the enable_content property for the Register() call
3) if possible, use data returned by the Register()/RegisterWithActivationKeys(), avoiding the additional GetPools() call, to show subscriptions that have been attached, if any

[0] https://github.com/candlepin/subscription-manager/pull/2860

PR: https://github.com/rhinstaller/anaconda/pull/4471

Checked that anaconda-34.25.2.5-1.el9 is in nightly compose RHEL-9.2.0-20230111.33
No regressions have been reported by automated tests.

Moving to VERIFIED

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 (anaconda bug fix and enhancement update), 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-2023:2223