Bug 1659571
Summary: | [RFE] On inplace upgrade to RHEL8, multipath configuration should be supported | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | afox <afox> |
Component: | leapp-repository | Assignee: | Leapp team <leapp-notifications> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Alois Mahdal <amahdal> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.8 | CC: | afox, agk, bmarzins, bmr, coughlan, heinzm, jbrassow, jmagrini, jzeleny, lilin, loberman, mbocek, michal.skrivanek, msnitzer, nsoffer, pdwyer, prajnoha, pstodulk, rhandlin, vfeenstr, yoyang, zkabelac |
Target Milestone: | rc | Keywords: | FutureFeature, Upgrades |
Target Release: | 7.8 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | leapp-repository-0.10.0-2.el7_8.noarch | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-14 10:56:04 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: | |||
Bug Blocks: | 1679810, 1784876 |
Description
afox@redhat.com
2018-12-14 16:54:58 UTC
I am seeing a problem with the current internal Leapp repos and a multipath configuration when upgrading from RHEL-7.6 to 8.0. The Upgrade RAMDISK fails to activate the system root devices and drops into the dracut shell. The cause isn't immediately clear but I've not carried out any real debugging yet. The host configuration is simple: one VirtIO disk for /boot, and a pair of iSCSI targets served by LIO/targetcli. Installation of RHEL7.6 to this set up proceeds as expected, leaving the volume group containing the root file system on the two multipath devices. The initial phase of Leapp seems to run as normal, but then fails booting the upgrade image. I've been able to reproduce the problem with booting into a leapp upgraded rhel8 system. Using iscsi devices like Comment 13 fails because the network isn't set up in time. But even if you can access the devices, multipath still fails because the multipath dracut module isn't present, but multipath is set up to run on the root and boot devices. If I mount all the missing filesystems and exit the emergency shell, and remake the initramfs with # dracut -f --add multipath everything works fine. So I believe that to fix this, the leapp tool needs to include the multipath dracut module in the initramfs it creates, if the rhel7 initramfs was including it. This bug should probably be reassigned to the leapp team, but I'm not sure what Component that goes under. A note from email exchange... I’ll ask Ben if he can come up with a simple command / script that would detect if multipath is in use on the RHEL7 system before upgrade. It might be as simple as checking the DM tables and grepping for ‘multipath’. # Tells you whether there is an active multipath instance on the machine e.g.> dmsetup table | grep multipath brassow That will pull in the multipath dracut module when it's not really needed (for non system directory cases). Instead you can just check if it's in the current initramfs. lsinitrd | grep "^multipath" should work for that. -Ben I've been instructed that the right location for this bug is RHEL7, leapp-repository. Switching there. I'm assigning this back to the leapp team, since the multipath actor work has been submitted https://github.com/oamg/leapp-repository/pull/473 Thanks Ben. The support for multipath has been released downstream in Leapp version 0.10.0: https://access.redhat.com/errata/RHBA-2020:1959. |