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 1835791 - System info shows "System Not Registered" even after registering the system via CLI
Summary: System info shows "System Not Registered" even after registering the system v...
Keywords:
Status: CLOSED DUPLICATE of bug 1796916
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-control-center
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-14 13:50 UTC by Poorani Sivakumar
Modified: 2023-12-15 17:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-08 11:44:13 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
After system is registered, check on the System Device info which still shows a Register button. (61.77 KB, image/png)
2020-05-14 13:50 UTC, Poorani Sivakumar 		no flags Details
Registration using button fails (76.71 KB, image/png)
2020-05-14 13:53 UTC, Poorani Sivakumar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5095241 0 None None None 2020-05-21 08:16:48 UTC

Description Poorani Sivakumar 2020-05-14 13:50:48 UTC 
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
Comment 1 Poorani Sivakumar 2020-05-14 13:53:41 UTC 
Created attachment 1688479 [details]
Registration using button fails
Comment 5 Tomas Popela 2021-01-08 11:44:13 UTC 

*** This bug has been marked as a duplicate of bug 1796916 ***
Note You need to log in before you can comment on or make changes to this bug.