Red Hat Bugzilla – Bug 1252848
system/kdump: Rewrite to better cover kdump/zipl case
Last modified: 2016-04-04 15:29:30 EDT
On s390x, if user installed kernel-kdump using installer UI (anaconda,
as opposed to installing the package later using eg. yum) but later
removed it using rpm/yum, system could end up with corrupted zipl.conf
(in some cases even unbootable).
Description of problem
Current implementation of system/kernel-kdump content is trying to help
user with above scenario by advicing them but also by attempting to fix
the situation. This has proved unreliable, too bold and potentially
causing more harm than good.
Replace content with new implementation based only on detecting,
explaining and advising on the problem, and leaving the solution up to
Version-Release number of selected component
Steps to Reproduce
1. Run anaconda installer and select kernel-kdump to be installed
2. On the new system, remove kernel-kdump using yum or similar
but do not update /etc/zipl.conf
3. Run preupg
4. Run redhat-upgrade-tool to upgrade to RHEL7
* Preupg says (in result.html or similar) it's planning to remove
* redhat-upgrade-tool removes kernel-kdump and attempts
to update zipl.conf
* Preupg raises HIGH risk and explains the situation in result.html.
Solution is left to user.
* If kdump is installed *and* present in zipl.conf,
=> two separate HIGH risks are issued.
* If kdump is installed *but not* present in zipl.conf,
=> one HIGH risk is issued.
* If kdump is neither installed *nor* present in zipl.conf,
=> no related HIGH risk is issued.
* In any case,
=> no preupgrade-scripts are generated.
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.