Red Hat Bugzilla – Bug 1259768
The RHSM addon should report background processing is ongoing and prevent early exit from Initial Setup until done
Last modified: 2017-08-01 15:18:42 EDT
Description of problem:
The Subscription Manager addon for Initial Setup does not indicate that the addon is doing important work in the background (registration & attach) that should not be interrupted and allows the user to exit the Initial Setup hub vie the "FINISH CONFIGURATION" button even when the background processing is still ongoing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. enter the RHSM addon in IS
2. enter credentials and click the "Register button"
3. a rpogress bar shows up on the screen
4. click the "Done" button in the upper left to return to the hub
(the same steps are valid even for attach phase)
The subscription manager status message on the hub still reads "System is not registered RHSM", the spoke is marked as completed (no yellow warning sign is displayed) and the "FINISH CONFIGURATION" button can be clicked.
The subscription manager status message indicates background processing is going on (something like "Registering system to RHSM" or "Attaching subscription"), spoke is not marked as completed (yellow warning sign is displayed) and the "FINISH CONFIGURATION" button can't be clicked (as long as at least one spoke is not complete, the "FINISH CONFIGURATION" button can't be clicked.
Spoke status message can be set using the "status" spoke property and the "completed" property is used to mark spoke completeness.
Hmm, current code will show 'completed' once registration finishes. But
the spoke is also not mandatory, so not sure of the implications.
deferring for consideration in rhel-7.3.0 due to schedule and severity
Created attachment 1272018 [details]
Message "System is registering to owner environment" is seen on spoke , while registration process is still in progress
[root@dhcp35-160 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.51.21-1
subscription management rules: 5.15.1
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.