Bug 2100467
| Summary: | System registration via GUI with activation keys fails with "Unknown arguments: dict_keys(['enable_content'])" | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Peter Stone <fedora-topics-562353> | ||||||||||
| Component: | gnome-settings-daemon | Assignee: | Kalev Lember <klember> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Tomas Pelka <tpelka> | ||||||||||
| Severity: | low | Docs Contact: | Marek Suchánek <msuchane> | ||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 9.0 | CC: | feborges, ptoscano, rstrode, tpelka, tpopela | ||||||||||
| Target Milestone: | rc | Keywords: | Triaged, ZStream | ||||||||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||||||||
| Hardware: | All | ||||||||||||
| OS: | All | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | gnome-settings-daemon-40.0.1-8.el9 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: |
.Subscription enrolling with Activation keys has been fixed
Previously, you could not enroll your Red Hat subscription in *Settings* using Activation keys. *Settings* displayed the following error after pressing btn:[Register]:
----
Failed to register system; Failed to RegisterWithActivationKeys: Unknown arguments: dict_keys(['enable_content'])
----
With this update, the problem has been fixed, and you can now enroll your subscription using Activation keys as expected in *Settings*.
|
Story Points: | --- | ||||||||||
| Clone Of: | |||||||||||||
| : | 2113960 (view as bug list) | Environment: | |||||||||||
| Last Closed: | 2022-11-15 10:37:59 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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 2113960 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Peter Stone
2022-06-23 12:54:51 UTC
Hello Peter, thanks for filing this bug for us. Can you please clarify what is the UI being used for the registration after the installation? The context here is that subscription-manager used to provide a page in the "Initial setup" wizard that appears when you graphically log in to RHEL for the first time after the installation. We stopped providing that page in RHEL 9, so I'm surprised you get something like that (and we did not have internal reports about this either). If possible, can you please attach screenshot(s) of what you get? Thanks in advance! Created attachment 1893172 [details]
message after boot
Created attachment 1893173 [details]
click on Subscription
Created attachment 1893174 [details]
write activation key and org ID then press Register
Created attachment 1893175 [details]
get this error message after pressing Register
@ptoscano I used the graphical UI via the GNOME Settings app to try to register the system. Screenshots with steps are attached. I had a chat with Felipe Borges from the Desktop Team (that maintains the GNOME integration for Subscriptions). It seems that the gnome-settings-daemon plugin adds "enable_content" as option for both the "Register" and "RegisterWithActivationKeys" D-Bus methods. The "enable_content" option is used to also attach the content after the registration (as the name says, "enable the content/repositories"). It is useful only when registering with means different than activation keys (e.g. username & password), as activation keys have already an attribute that specifies whether perform this automatic content enablement upon successful registration. There was a request to make "enable_content" usable with "RegisterWithActivationKeys" as well, however it was rejected: bug 2059447. Because of this, I'm reassigning the bug to gnome-settings-daemon, to make sure "enable_content" is used as option only when registering using "Register". 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 (gtk4 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-2022:8218 |