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:
When running anaconda in cmdline mode (appending inst.cmdline) and using a kickstart which includes a

%post --erroronfail
…
%end

snippet, then anaconda will prompt for input if the snippet fails.


Version-Release number of selected component (if applicable):
CentOS 7 version, quite sure in Fedora as well

How reproducible:
Always

Steps to Reproduce:
1. Failing postlet and anaconda with inst.cmdline
2.
3.

Actual results:
anaonda prompts for input

Expected results:
anaconda shows the error and shutsdown the host

Additional info:

(In reply to Fabian Deutsch from comment #0)
> Version-Release number of selected component (if applicable):
> CentOS 7 version, quite sure in Fedora as well

This problem does not occur in Fedora.

This just needs a cherry pick of 8f361ad0539763f90a97f90443185f8726f2a553.

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://rhn.redhat.com/errata/RHEA-2016-2158.html