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:
Firstboot require reboot before the subscribe result was showed
Version-Release number of selected component (if applicable):
subscription-manager-gui-1.10.6-1.el7
subscription-manager-1.10.6-1.el7
subscription-manager-firstboot-1.10.6-1.el7
python-rhsm-1.10.6-1.el7
How reproducible:
always
Steps to Reproduce:
1.Install a new RHEL7 system then go to the firstboot
2.In the subscription page select "Yes, I'd like to register now" option and press "Finish".
3.Press "Finish" again to enter the next page then input the user name and password and press "Finish"
4.In the subscription select page press "Finish"
Actual results:
When first run the firstboot, a pop-up window jump out and require a reboot, no subscription sucessful page will be shown. please see the attachment.
When use cmd to run firstboot, the firstboot progress just disappeared without any information.
Expected results:
There should be a subscription succeed page to let the customer know their operation is right. Now the first boot action is confused, don't know the subscription is successful or not.
Additional info:
Going to close this as we cannot fix in time for 7.1, and 7.2 will no longer use the current firstboot code. We will be moving to the new anaconda installer modules.