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 | |||
: | 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
The fix is available in a pull request: https://github.com/rhinstaller/anaconda/pull/985 I was able to verify this bug on RHEL-7.4-20170421.1 with anaconda-21.48.22.110-1.el7. 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 |