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 1796916 - Notification appears with incorrect "system not registered - register to get updates" message on RHEL8.2 when locale is non-English
Summary: Notification appears with incorrect "system not registered - register to get ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-settings-daemon
Version: 8.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Michael Boisvert
URL:
Whiteboard:
: 1830224 1831784 1835791 1842697 (view as bug list)
Depends On: 1870567
Blocks: 1801570 1894575
TreeView+ depends on / blocked
 
Reported: 2020-01-31 13:47 UTC by Misha Ramendik
Modified: 2024-03-25 18:12 UTC (History)
37 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1870837 1872457 (view as bug list)
Environment:
Last Closed: 2021-05-18 14:38:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Registration UI (34.27 KB, image/png)
2020-02-03 20:11 UTC, Misha Ramendik 		no flags Details
The pop-up message that the system is not registered (16.36 KB, image/png)
2020-02-13 16:22 UTC, Misha Ramendik 		no flags Details
subman test, system unregistered after test package (59.16 KB, image/png)
2020-08-20 19:48 UTC, Steve Barcomb 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5060361 0 None None None 2020-10-07 07:41:40 UTC
Red Hat Knowledge Base (Solution) 5095241 0 None None None 2023-10-06 20:02:08 UTC

Description Misha Ramendik 2020-01-31 13:47:03 UTC 
Description of problem:

I deployed RHEL 8.2 Dec 19 engineering build. I did not register it at install time as the Wi-Fi was not working at install time (a common occurrence in Linux installers).

After the system started, I attempted to register using the GUI. However, the registration GUI required an "organization" as well as my username and password. I tried redhat, Red Hat, redhat.com  to no avail.

Then I used "subscription-manager register" on the CLI, entered my RH Developer username and password, and this succeeded. I then issued the command "subscription-manager attach" and the system started using repositories successfully.

However, the GUI (Gnome shell) now intermittently reports "system not registered - register to get updates". At other points it reports that the system is registered.

Version-Release number of selected component (if applicable):

# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.9.21-1
subscription management rules: 5.37
subscription-manager: 1.26.9-1.el8



How reproducible:

Did not try to reproduce, as a fresh deployment would be required.

Steps to Reproduce:
1. Deploy RHEL with the installer without registering at install time. 
2. Click the GUI prompt that asks to register.
3. Enter a Red Hat associate's dRH Developer ID, enabled for software subscriptions.

Actual results:

An "Organization" is required and blank, Red Hat, redhat, and redhat.com are not accepted as values. And when you complete registration using the CLI, you intermittently get "system not registered" in GUI.

Expected results:

Registering succeeds and the GUI does not claim the system is not registered.

Additional info:
Comment 2 Misha Ramendik 2020-02-03 20:11:44 UTC 
Created attachment 1657419 [details]
Registration UI
Comment 3 Misha Ramendik 2020-02-03 20:14:06 UTC 
I have just added a screenshot of the regisration UI. To reach this UI, I search Subscription in the activity screen, open it, and click Register (n a fresh install that is not registered - done in a VM).

I enter my Red Hat portal account (mramendi) in Login and Password, cloch Register, and see the error message: "You must specify an organization for new units".
Comment 6 Misha Ramendik 2020-02-10 20:20:48 UTC 
@chris snyder there is a third issue as well. I have registered with the command line subscription manager. but I am still getting "System not registered" notification in Gnome.
Comment 7 Rehana 2020-02-12 13:05:27 UTC 
(In reply to Misha Ramendik from comment #6)
> @chris snyder there is a third issue as well. I have registered with the
> command line subscription manager. but I am still getting "System not
> registered" notification in Gnome.

Hi Misha,

We thought the bug 1744196 covered that incorrect status showing on the GUI issue, please let us know if thats not the same case. 

thanks,
Rehana
Comment 8 Misha Ramendik 2020-02-12 14:27:27 UTC 
@Rehana I think it is a different case because I do not launch subscription-manager. The message is a system notification I get from time to time without launching anything.

Besides the message is different - "System not registered" not "could not get status".

When I click the message, the UI is launched but there it says the system is registered.
Comment 9 Rehana 2020-02-13 04:40:39 UTC 
(In reply to Misha Ramendik from comment #8)
> @Rehana I think it is a different case because I do not launch
> subscription-manager. The message is a system notification I get from time
> to time without launching anything.
> 
> Besides the message is different - "System not registered" not "could not
> get status".
> 
> When I click the message, the UI is launched but there it says the system is
> registered.

Thanks Misha for the details , it looks like you are getting the rhsm-icon pop up message on the screen. I will bring this bug to triage meeting today and check with the team if they need a separate bug to track this or not. 

Thanks for all the help 

Rehana
Comment 10 Misha Ramendik 2020-02-13 16:22:38 UTC 
Created attachment 1662986 [details]
The pop-up message that the system is not registered

I managed to catch a screenshot of the pop-up message in question.
Comment 12 Rehana 2020-05-04 14:34:59 UTC 
*** Bug 1830224 has been marked as a duplicate of this bug. ***
Comment 16 Rehana 2020-06-19 15:00:49 UTC 
Based on the comment 15 , moving to gnome3-control team
Comment 18 Kalev Lember 2020-06-25 07:33:46 UTC 
Moving to gnome-settings-daemon.

Richard, can you take a look? The notification comes from your subscription manager integration code in gnome-settings-daemon.
Comment 26 Richard Hughes 2020-07-23 12:53:01 UTC 
Back a bit:

If this is the output of subscription-manager then are we registered with a valid subscription or not?
  
     $ subscription-manager register
     $ # success returned!
     $ subscription-manager status
     +-------------------------------------------+
     System Status Details
     +-------------------------------------------+
     Overall Status: Invalid

On my test box where I have a subscriptions set up correctly I get:

     +-------------------------------------------+
     System Status Details
     +-------------------------------------------+
    Overall Status: Current

Quoting Bastien, who debugged this a bit today:

> I don't see how the notification can have the right information here.
> I looked through the subscription-manager source code as well, and couldn't
> find anything that would indicate that "invalid" is anything but "invalid"
> as a status.

If invalid is something we should ignore (or if we should treat invalid==current) for the purposes of the GUI notification then that's a change we could make, but it's certainly not expected that you register with valid credentials and then the system status to come back as invalid.

My *guess* would be that registering with --auto-attach is required to convert the status from invalid to current which is why we didn't spot this during QA. If anyone can find any relevant subman documentation about the status enums please say. Someone from the subman team might be able to help here.
Comment 27 Richard Hughes 2020-07-23 13:20:25 UTC 
Reassigning so we can get some input from the subman team. If we do need to ignore "invalid" it would be nice to see some documentation for the different status values returned.
Comment 28 ilopeman 2020-07-23 13:48:43 UTC 
In my case "Overall Status" is "Actual" (current in spanish):

subscription-manager status
+-------------------------------------------+
   Información de estatus del sistema
+-------------------------------------------+
Overall Status: Actual 

And i also receive "System not registered" notification in Gnome
Comment 30 Richard Hughes 2020-07-24 12:30:46 UTC 
Mei is very much correct, and provided the critical part of the puzzle:

On a system that is not configured as en_US or en_GB you can confirm this bug by doing the following on a ja_JP machine:

   gdbus call --system --dest com.redhat.RHSM1 --object-path /com/redhat/RHSM1/Entitlement --method com.redhat.RHSM1.Entitlement.GetStatus \"\" \"\"

To verify youself, change /etc/locale.conf to:

    LANG="fr_FR.UTF-8"

...and then reboot. With this change, the output is

    ('{"status": "Actuel", "reasons": {}, "valid": true}',)

And of course, the localized "Actuel" doesn't match the expected "Current" in gsd-subman and we correctly fall back to the "unknown" status.

Needless to say, D-Bus methods shouldn't be returning localised enumerated values like this. A D-Bus interface reports enumerated values which are translated by the front end tool, so if the system locale is in German and the user session is in French then the messages should come out with the latter language, not the former. I suspect this is because subscription manager isn't being run with something like C.UTF-8, but that would probably fix this bug too.

I also really don't think there's any way the desktop should (or could) try to parse every languages version of "current". The fix needs to be in subscription-manager.
Comment 51 Carlos Santos 2020-08-18 21:28:52 UTC 
There is a quick and dirty way to make the annoying message go away:

    # chmod -x /usr/libexec/gsd-subman

Obviously this cannot be suggested as a general workaround, since it does not survive a system upgrade.
Comment 61 Steve Barcomb 2020-08-20 19:48:31 UTC 
Created attachment 1712075 [details]
subman test, system unregistered after test package
Comment 74 Robert Scheck 2020-10-08 07:34:42 UTC 
Cross-filed case 02771021 at the Red Hat customer portal in order to hopefully get a real fix (rather a workaround) as errata update soon, given this bug did not lead to a bugfix update for 8+ months now.
Comment 76 Misha Ramendik 2020-11-30 19:19:05 UTC 
I am the original reporter. I have not seen this happen since the update to RHEL 8.3.
Comment 77 Tomas Popela 2021-01-08 11:36:44 UTC 
*** Bug 1831784 has been marked as a duplicate of this bug. ***
Comment 78 Tomas Popela 2021-01-08 11:37:37 UTC 
*** Bug 1842697 has been marked as a duplicate of this bug. ***
Comment 79 Tomas Popela 2021-01-08 11:44:13 UTC 
*** Bug 1835791 has been marked as a duplicate of this bug. ***
Comment 80 hasuzuki 2021-01-15 02:14:12 UTC 
The problem solve after updating gnome-settings-daemon from 3.32.0-9.el8.x86_64 to 3.32.0-11.el8.x86_64 in RHEL8.2.
Comment 88 Michael Boisvert 2021-02-11 15:59:41 UTC 
I tested the latest packages on RHEL8.4 and it looks like an expected user experience. With a registered but not attached subscription, the gnome GUI shows "Registered system" as does the subscription-manager and CLI. I also tried multiple different locales. Jiri, could you test the actual subscription parts and we can move this bug to verified?
Comment 89 Michael Boisvert 2021-02-16 14:26:46 UTC 
(In reply to Michael Boisvert from comment #88)
> I tested the latest packages on RHEL8.4 and it looks like an expected user
> experience. With a registered but not attached subscription, the gnome GUI
> shows "Registered system" as does the subscription-manager and CLI. I also
> tried multiple different locales. Jiri, could you test the actual
> subscription parts and we can move this bug to verified?

I ended up testing it myself using gnome-settings-daemon-3.32.0-13.el8.x86_64 gnome-control-center-3.28.2-26.el8.x86_64. My statements above still ring true and once the attachments to a subscription are made, the gnome GUI, sub-man GUI and CLI all show proper subscriptions. I see no error messages about bad or expired registrations and all messages/information provided shows accurate status of the current subscription. I tested the subscription process using RHEL8.3 and an Ethel account for the subscriptions as this was the only path I could get a real confirmed subscription through the same type of channels customers would be using.
Comment 91 errata-xmlrpc 2021-05-18 14:38:17 UTC 
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 (Moderate: GNOME security, 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/RHSA-2021:1586
Note You need to log in before you can comment on or make changes to this bug.