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.

Bug 1412538

Summary:	[RFE] %onerror from pykickstart
Product:	Red Hat Enterprise Linux 7	Reporter:	Samantha N. Bueno <sbueno>
Component:	anaconda	Assignee:	Vendula Poncova <vponcova>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:	Filip Hanzelka <fhanzelk>
Priority:	medium
Version:	7.2	CC:	cww, jstodola, pkotvan, release-test-team-automation, riehecky, rvykydal, salmy, srandhaw, vponcova
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-21.48.22.102-1	Doc Type:	Enhancement
Doc Text:	Kickstart installation failure automatically triggers `%onerror` scripts This enhancement makes sure that the `%onerror` sections in a kickstart file are run if the Anaconda installation fails. The scripts can be used to collect logs automatically for further examination. As a result of this update, when a traceback or another fatal error occurs during the installation, the installer performs the `%onerror` scripts and the `%traceback` scripts check if the error was caused by a traceback.	Story Points:	---
Clone Of:	1367663
Clones:	1428469 (view as bug list)		Environment:
Last Closed:	2017-08-01 08:53:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1367663
Bug Blocks:	1298243, 1395321, 1428469

Comment 1 Samantha N. Bueno 2017-01-12 08:56:07 UTC

Required change due to pykickstart bug 1367663.

From Chris:
"""
The anaconda portion is this:                                                                     
                                                                                                  
https://github.com/rhinstaller/anaconda/commit/e470d17cce407a63cea65450f33666b16dcb390a           
                                                                                                  
But that would probably be very different on rhel7-branch.                                        
Conceptually, it's pretty easy to do though.
"""

Comment 3 Vendula Poncova 2017-03-08 09:56:27 UTC

The fix is available in a pull request: https://github.com/rhinstaller/anaconda/pull/985

Comment 5 Peter Kotvan 2017-04-25 12:56:47 UTC

I was able to verify this bug on RHEL-7.4-20170421.1 with anaconda-21.48.22.110-1.el7.

Comment 9 errata-xmlrpc 2017-08-01 08:53:21 UTC

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:2293