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 2059447 - Support enable_content also for RegisterWithActivationKeys() DBus method
Summary: Support enable_content also for RegisterWithActivationKeys() DBus method
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: subscription-manager
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-01 03:27 UTC by Martin Kolman
Modified: 2022-04-05 10:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-05 10:39:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-114078 0 None None None 2022-03-01 03:34:01 UTC

Description Martin Kolman 2022-03-01 03:27:46 UTC
Support for the enable_content property has been added for the Register() DBus method, that makes it possible to register a system with username & password.

If the enable_content property is set to True, auto-attach no longer needs to be called explicitly and Subscription Manager will transparently handle all the necessary calls automatically, including taking care of the registration happening in Simple Content Access mode or legacy Entitlement Mode.

This has the potential to significantly simplify the code of RHSM DBus API clients, such as Anaconda, as no longer multiple APIs will have to be called and just one call will be enough. It will also make it possible to finally drop support for auto-attach being called in SCA mode.

Unfortunately, it looks like so far only the Register() DBus method properly supports the enable_content property, but the other registration method - RegisterWithActivationKeys - does not. This difference in behaviour would be quite a significant problem for Anaconda, as the old complicated behaviour would have to be kept for RegisterWithActivationKeys() and the new one supported for Register().

The lack of proper support for enable_content is apparently somehow related to auto-attach behavior/flag of some activation keys:


"When D-Bus method RegisterWithActivationKeys() is used, then
enable_content is ignored, because it auto-attach cannot be
used together with activation keys"


Anaconda has been always calling auto-attach after *every* RegisterWithActivationKeys() call (as well as after every Register() call) since RHEL 8.2, without any known issues being reporter as the result of this behaviour. Also as far as I know while some activation keys can have the auto-attach flag set (thus auto-attach already happens for these keys at registration time & we have seen this happen on real systems), there are also real keys that do not have this flag set and without auto-attach being used will not result in a properly subscribed system.

This has also been discussed on the regular Anaconda-RHSM-DNF sync meeting, with the conclusion being that there is really nothing preventing RegisterWithActivationKeys() fully supporting enable_content & making the life easier for all RHSM DBus API clients, not just Anaconda.

As an action item from the meeting, I have created this bug to track progress on enable_content being supported by RegisterWithActivationKeys() in the RHSM DBus API.


Note You need to log in before you can comment on or make changes to this bug.