Bug 1835791
| Summary: | System info shows "System Not Registered" even after registering the system via CLI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Poorani Sivakumar <psivakum> | ||||||
| Component: | gnome-control-center | Assignee: | Carlos Garnacho <cgarnach> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 8.2 | CC: | ayadav, lijli, redakkan, sgajendr, shivagup, tpopela | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | 8.0 | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-01-08 11:44:13 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1688479 [details]
Registration using button fails
*** This bug has been marked as a duplicate of bug 1796916 *** |
Created attachment 1688466 [details] After system is registered, check on the System Device info which still shows a Register button. Description of problem: System Device info showing as "System Not Registered" even after registering the system via command line. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 8.2 How reproducible: Steps to Reproduce: 1. Register the system using command #subscription-manager register 2. Once it gets registered, check on the system device info which still shows a Register button and displays "System Not Registered". 3. When we register using the button it gives error "Failed to register: The system is already registered" 4. Once the system is attached with any subscription, the page shows "Registered System" Actual results: The system device info shows "System Not Registered" after registration and before attaching subscriptions Expected results: The info needs to show as System not subscribed once registered and instead of Register button, Subscribe button must be present. Additional info: content from rhsm.log while register using the button in GUI: 2020-05-14 01:58:47,227 [DEBUG] rhsm-service:2395:MainThread @register.py:53 - Attempting to create new domain socket server 2020-05-14 01:58:47,230 [DEBUG] rhsm-service:2395:MainThread @register.py:58 - DomainSocketServer created and listening on "unix:abstract=/var/run/dbus-fCsfcwMIIq,guid=9999394a09fdb19331534a765ebcde17" 2020-05-14 01:58:47,544 [DEBUG] rhsm-service:2395:MainThread @server.py:223 - New connection: <dbus.connection.Connection object at 0x7f8946ab0f68> 2020-05-14 01:58:47,592 [ERROR] rhsm-service:2395:MainThread @util.py:41 - This system is already registered Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/rhsmlib/dbus/util.py", line 38, in dbus_handle_exceptions ret = func(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/rhsmlib/dbus/objects/register.py", line 110, in Register raise dbus.DBusException("This system is already registered") dbus.exceptions.DBusException: This system is already registered 2020-05-14 01:58:47,623 [DEBUG] rhsm-service:2395:MainThread @server.py:227 - Closed connection: <dbus.connection.Connection object at 0x7f8946ab0f68> 2020-05-14 01:58:47,623 [DEBUG] rhsm-service:2395:MainThread @server.py:231 - No connections remain