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:
Observed that  when no/wrong user details were given in the firstboot subscription register screen, firstboot screen was send to background/minimised 

Version-Release number of selected component (if applicable):
subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.8.29-1
subscription-manager: 1.10.4-1.el7
python-rhsm: 1.10.3-1.el7


How reproducible:
4/4

Steps to Reproduce:
1.Launch firstoot
2.move to subscription register screen
3.click forward without entering the credentials --(A)
4.Issue wrong credentials and click next (B)

Actual results:
Observed that during both the cases (A) & (B) when the error message screen pops up the main First boot screen was getting minimised or send to background and after clicking "Ok" on the msg window the firstboot screen didnt come up

Expected results:
The error screen should display on the main first boot screen and after clicking "Ok" on the error message screen the control should go back to first boot screen 

Additional info:

Need to verify but I suspect this is just how firstboot behaves when an error is thrown and you're running it manually *after* logging into the system. (note that this is not how firstboot is normally meant to be used, only something we do for dev/QE testing)

I have seen this behaviour for popups after hardware profile reporting screens in firstboot, I think it's just an issue with how firstboot behaves if you're already logged in.

Need to test this but suspect this is a close wontfix or cantfix.

Moving bugs from 7.0 to 7.1

Acking 7.1

Closing as firstboot is largely unmaintained now, and we are only considering critical fixes. 

Will be addressed for 7.2 by the planned port to new anaconda installer modules. More details in comment #1.