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.
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):
subscription-manager-initial-setup-addon.x86_64 0:1.15.9-7.el7
How reproducible:
always
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)
Actual results:
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.
Expected results:
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.
Additional info:
Spoke status message can be set using the "status" spoke property and the "completed" property is used to mark spoke completeness.
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
subscription-manager: 1.19.7-1.el7
python-rhsm: 1.19.4-1.el7
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/RHBA-2017:2083