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:


Version-Release number of selected component (if applicable):
anaconda 21.48.22.143-1

How reproducible:
Unknown.

Steps to Reproduce:
1. Run anaconda from the cmdline with --cmdline (in this case it is being started from lorax-composer).
2. Something (still unknown) caused bootloader installation to fail.
3. Anaconda didn't exit with an error even though it logged a traceback
3.

Actual results:
Anaconda logs a traceback, but hangs instead of exiting with an error.

Expected results:
Exit with a non-zero error code.

Created attachment 1457939 [details]
anaconda.log

Created attachment 1457940 [details]
program.log

Created attachment 1457941 [details]
storage.log

Created attachment 1457942 [details]
packaging.log

The actual crash seems to be rhbz#1497918 but I'm more concerned with it not exiting than the actual crash.

Hi Brian,

You have how reproducible set to unknown. Do you know now if you are able to reproduce that issue or if that was some race condition?

It has happened both times I've tried. I think the exception handling for that chunk of code isn't doing the cmdline check for some reason and is waiting for user input:

16:36:33,074 ERR anaconda: The following error occurred while installing the boot loader. The system will not be bootable. Would you like to ignore this and continue with installation?                                                      

instead of just exiting.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.