Bug 1965027

Summary: Registration Fails with "You must specify an organization for new units" - please add organization selection menus to the registration module in anaconda and cockpit
Product: Red Hat Enterprise Linux 8 Reporter: Samson Wick <swick>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.3CC: jstodola
Target Milestone: beta   
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-06-01 17:20:41 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Samson Wick 2021-05-26 15:02:02 UTC
Description of problem:
System registration to the CDN fails with the GUI tools Anaconda and Cockpit fails with the message "You must specify an organization for new units" if attempted with an account that is part of more than one logical organization.

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


How reproducible:


Steps to Reproduce:
1. Attempt to register any RHEL 8 system using Anaconda or Cockpit with an account that is part of more than one organization.
2. Observe that registration fails with "You must specify an organization for new units" and that neither tool gives you any opportunity to select an organization before attempting registration.


Actual results: registration fails with "You must specify an organization for new units".


Expected results: registration succeeds, OR registration dialog allows you to select an organization prior to attempt


Additional info:
This has been a known issue since at least September 2020 (See: https://access.redhat.com/discussions/5363891) From what I can tell at some point the CDN registration process began requiring an organization when registration is performed through a GUI and the account is a member of more than one organization.  While I can surmise the purpose of this change is to allow for correct subscription allocation by organization, the tools should have been updated to handle the scenario before the CDN was updated to reject registration requests without an "organization" value.

"subscription-manager register" run on the command line succeeds for the same user account without requiring the user to provide an organization, but this workaround has some considerable drawbacks.  Firstly it defeats the purpose of keeping subscriptions separated between organizations because it just seems to arbitrarily choose an organization. Secondly, the registration information is still not recognized by Cockpit when subscription-manager was used to entitle the system so anyone using Cockpit to verify subscription status will be misled into believing the system is not registered.

This request is to address the disconnect between the GUI registration tools (Anaconda and Cockpit) and the CDN behavior by adding dialog options to either select an organization prior to registration, or a "choose one for me" option which uses the same logic that "subscription-manager register" does.  I also strongly believe that the CDN behavior should be updated to stop rejecting registration requests without an "organization" value until this has been fixed in Anaconda and Cockpit.

Comment 1 Jan Stodola 2021-05-26 15:14:05 UTC
Hi Samson,
what RHEL-8 version do you use? Can you confirm you can reproduce this problem on RHEL-8.4? The problem should be fixed there by bug 1753236.
Are you registering against a Satellite?

Comment 2 Samson Wick 2021-06-01 15:31:25 UTC
(In reply to Jan Stodola from comment #1)
> Hi Samson,
> what RHEL-8 version do you use? Can you confirm you can reproduce this
> problem on RHEL-8.4? The problem should be fixed there by bug 1753236.
> Are you registering against a Satellite?

I observed this on RHEL 8.3 registering it against the CDN, not Satellite.  I initially encountered trying to register RHV Hosts and RHEL 8.3 was the current version provided at the time of reporting this issue.  I will re-check with RHEL 8.4 and report.

Comment 3 Samson Wick 2021-06-01 16:13:14 UTC
I have confirmed this has been resolved in the latest RHEL 8.4 ISO - I was just now able to successfully register via Anaconda without encountering the error.  However with the latest current version of RHVH (RHVH-4.4-20210331.0-RHVH-x86_64-dvd1.iso) registration still fails however now it is with a different message: "AttributeError: 'NoneType' object has no attribute 'Type'"   I suspect this is because the latest RHVH ISO has not been updated with the fixes implemented in RHEL 8.4.

Comment 4 Jan Stodola 2021-06-01 17:20:41 UTC
Thank you for the confirmation that the problem is resolved for you when using RHEL-8.4.
I will close this bug as a duplicate of bug 1753236, which fixed this problem.

The other failure you are seeing with RHVH is reported as bug 1941578 and it is planned to be fixed in RHEL-8.5.

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