Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionMatthias Clasen
2019-06-13 13:50:07 UTC
+++ This bug was initially created as a clone of Bug #1698536 +++
We want to offer a page in gnome-initial-setup to let users enroll their system.
The backend functionality for this needs to be added in gnome-settings-daemon.
Even after I have registered to subscription management, I'm still getting the notifications about not being registered.
I have registered through control-center dialog and then also through subscription-management cli and in both cases I'm getting false notifications that I need to register.
When I go to control-center About tab, the systems shows to be registered, also confirmed by sm cli status command.
When I registered through control-center I got confirmation notification that my system is registered, but when I used the sm cli command to register I got notification that my system is NOT registered.
Also the icon in both positive and negative notifications is the same, which is quite confusing.
Another issue is that subman only knows how to register but is not able to handle situation where the system is registered but has no subscriptions attached. Then the registration in control-center fails with "Failed to Register: This system is already registered"
e.g. when you remove subscriptions attached to a system # subscription-manager remove --all
gnome-settings-daemon-3.32.0-4.el8
gnome-control-center-3.28.2-5.el8
Richard, can you take a look at the g-s-d notifications issue? The g-c-c side I did seems to be working as expected here.
Also, we also need to make sure that the gnome-settings-daemon and gnome-control-center side of things go out together, or neither of them goes out. Otherwise we end up with a situation where g-s-d notifications appear, but we don't have any UI to actually subscribe.
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, 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/RHSA-2020:1766