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 1279019 - bootloader update failure is not detected
Summary: bootloader update failure is not detected
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-upgrade-tool
Version: 6.7
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Bocek
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-07 08:18 UTC by Alois Mahdal
Modified: 2019-07-01 15:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-01 15:31:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alois Mahdal 2015-11-07 08:18:39 UTC 
Description of problem
======================

It's possible that even if bootloader update fails, redhat-upgrade-tool
will still finish with zero status and advice to go on with the upgrade.

This happens in one of use cases relevant to bug 1273867: a bug in
anaconda can lead to invalid record in zipl.conf.  If that happens,
zipl, called by r-u-t to to update bootloader will fail, but r-u-t does
not detect this.

    [...]
    HOOK-pkgdowngrades: INFO: DOWNGRADE: enforcing package installation 'tzdata.noarch'
    HOOK-pkgdowngrades: INFO: done
    Error: Image file '/boot/vmlinuz-2.6.32-573.el6.s390x.kdump' in section 'linux-kdump-2.6.32-573.el6.s390x.kdump': No such file or directory
    Error: Image file '/boot/vmlinuz-2.6.32-573.el6.s390x.kdump' in section 'linux-kdump-2.6.32-573.el6.s390x.kdump': No such file or directory
    redhat_upgrade_tool.sysprep WARNING: can't determine version of kernel image '/boot/vmlinuz-redhat-upgrade-tool'
    Error: Image file '/boot/vmlinuz-2.6.32-573.el6.s390x.kdump' in section 'linux-kdump-2.6.32-573.el6.s390x.kdump': No such file or directory
    Error: Image file '/boot/vmlinuz-2.6.32-573.el6.s390x.kdump' in section 'linux-kdump-2.6.32-573.el6.s390x.kdump': No such file or directory
    Continue with the upgrade [Y/N]? getting boot images...
    setting up update...
    testing upgrade transaction
    setting up system for upgrade
    Finished. Reboot to start upgrade.


Version-Release number of selected component
============================================

preupgrade-assistant-2.1.1-5.el6
preupgrade-assistant-contents-0.6.41-1.el6
redhat-upgrade-tool-0.7.43-1.el6


How reproducible
================

Always


Steps to Reproduce
==================

There are probably much more ways to have the bootloader update fail.
One of them, similar to the mentioned case:

 0. Install preupg et al. on an s390x machine

 1. Open /etc/zipl.conf, and add a boot record with `image=` path pointing
    to a non-existent file

 2. Run redhat-upgrade-tool with necessary parameters


Actual results
==============

redhat-upgrade-tool will finish with zero status, suggesting to re-boot
to start the upgrade


Expected results
================

redhat-upgrade-tool should detect the problem and gracefully exit
Comment 2 Alois Mahdal 2015-11-11 02:14:50 UTC 
Another case I managed to find by accident: is if you accidentally use different arch's repositories.

In this case, the message from sysprep is quite subtle:

    [....]
    HOOK-pkgdowngrades: INFO: DOWNGRADE: enforcing package installation 'python-requests.noarch'
    HOOK-pkgdowngrades: INFO: done
    redhat_upgrade_tool.sysprep WARNING: can't determine version of kernel image '/boot/vmlinuz-redhat-upgrade-tool'
    Continue with the upgrade [Y/N]? getting boot images...
    setting up update...
    testing upgrade transaction
    setting up system for upgrade
    Finished. Reboot to start upgrade.

In my case, it was s390x on x86_64.  Needless to say, the reboot is not possible with this setup; user will need to (manually?) select the original RHEL in bootloader menu.

(In theory, if a bootable combination existed, results could be worse---well, I don't think there is, at least not in *->RHEL7 but in future...)
Comment 3 Michal Bocek 2019-07-01 15:31:33 UTC 
Closing this bugzilla as the component is under a maintenance mode in which the maintainers are going to fix only critical bugs. If you consider the bugzilla critical, feel free to reopen the bug with an explanation.
Note You need to log in before you can comment on or make changes to this bug.