Bug 1796916

Created attachment 1657419 [details]
Registration UI

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".

@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.

(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

@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.

(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

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.

*** Bug 1830224 has been marked as a duplicate of this bug. ***

Based on the comment 15 , moving to gnome3-control team

Moving to gnome-settings-daemon.

Richard, can you take a look? The notification comes from your subscription manager integration code in gnome-settings-daemon.

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.

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.

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

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.

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.

Created attachment 1712075 [details]
subman test, system unregistered after test package

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.

I am the original reporter. I have not seen this happen since the update to RHEL 8.3.

*** Bug 1831784 has been marked as a duplicate of this bug. ***

*** Bug 1842697 has been marked as a duplicate of this bug. ***

*** Bug 1835791 has been marked as a duplicate of this bug. ***

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.

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?

(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.

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