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.

Bug 2057437

Summary: Un-actionable error message during registration failure: Auto-attaching is not allowed in simple content access mode
Product: Red Hat Enterprise Linux 9 Reporter: Timothée Ravier <travier>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: jstodola
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-23 12:06:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Timothée Ravier 2022-02-23 11:56:59 UTC
Description of problem:

During the installation of a RHEL 9.0 pre-release system, I tried registering the system during the installation using my company Red Hat account. This failed with the following error message:

Auto-attaching is not allowed in simple content access mode

(see screenshot)

Searching for this error leads to https://access.redhat.com/articles/simple-content-access which does not explain how I should register my system during the installation process.

I think that the error should include a link to a documentation page with the relevant explanation.

Version-Release number of selected component (if applicable):

ISO: RHEL-9.1.0-20220215.3-x86_64-dvd1.iso

How reproducible:

Always as far as I could try. Tried once in French, once in English.

Steps to Reproduce:
1. Start installation process
2. Select Registration poke
3. Try registering with a company Red Hat account

Actual results:

I have the error message mentioned above & in screenshot.

Expected results:

I get a link to a documentation page explaining what I should do.

Additional info:

Comment 1 Jan Stodola 2022-02-23 12:06:10 UTC
Hello, this should be fixed in a later nightly composes (for example RHEL-9.0.0-20220221.2 with subscription-manager-1.29.26-1.el9).
This was caused by a change in subscription-manager and has been fixed in bug 2049139.

I'm closing this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 2049139 ***

Comment 2 Timothée Ravier 2022-02-23 14:48:42 UTC
I can confirm that this is fixed in RHEL-9.1.0-20220222.1-x86_64-dvd1.iso. Thanks!