Description of problem: When having systems configured with ZFCP instead of DASD, the disks are not seen while rebooting because `/etc/zfcp.conf` is missing in the initramfs. Additionally, when zipl-switch-to-blscfg executes to convert to BLS, the execution fails because /dev nodes are not available in the container. See https://github.com/oamg/leapp-repository/pull/983 for the final fixes. Version-Release number of selected component (if applicable): leapp-upgrade-el7toel8-0.16.0-8.el7_9.noarch How reproducible: Always with ZFCP
*** Bug 1969883 has been marked as a duplicate of this bug. ***
------- Comment From tstaudt.com 2022-09-02 04:56 EDT------- We opened Red Hat Bug 2096160 - RHEL7.9/8.6 - [s390x] system not bootable after in-place upgrade from RHEL7.9 to RHEL8.6 on s390x using SCSI disk (leapp-repository/Extras) to further address the topic and closed this bug. Thanks, everyone.
------- Comment From tstaudt.com 2022-11-09 04:44 EDT------- Reopening as this is now linked to Red Hat Bug 2140563 - ZFCP systems fail to convert + issue with zipl-switch-to-blscfg
Created attachment 1924169 [details] console_output_after_reboot
Created attachment 1924170 [details] Output of first "leapp upgrade" command
Created attachment 1924171 [details] Output of secound "leapp upgrade" command.
Created attachment 1924172 [details] Output of "leapp preupgrade" command.
------- Comment From thorsten.diehl.com 2022-11-14 05:44 EDT------- I tested leapp upgrade on s390x SCSI disk with leapp.noarch 0:0.15.0-100.20221019062411522869.master.6.g14fae66.el7 leapp-upgrade-el7toel8.noarch 0:0.17.0-100.20221030153816680418.master.18.g6ec9f0a.el7 leapp-data-19 plus manually applied patches from https://github.com/oamg/leapp-repository/pull/983 That brought me with leapp preupgrade, upgrade and reboot to a RHEL8.6 system for the very first time. So, the code in PR #983 seems to help here. So far, so good. After 3 minutes I rebooted that system, and it felt into Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0). No idea what I did wrong. Retest required, when PR has been implemented.
(In reply to IBM Bug Proxy from comment #13) > ------- Comment From thorsten.diehl.com 2022-11-14 05:44 EDT------- > I tested leapp upgrade on s390x SCSI disk with > leapp.noarch 0:0.15.0-100.20221019062411522869.master.6.g14fae66.el7 > leapp-upgrade-el7toel8.noarch > 0:0.17.0-100.20221030153816680418.master.18.g6ec9f0a.el7 > leapp-data-19 > plus manually applied patches from > https://github.com/oamg/leapp-repository/pull/983 > That brought me with leapp preupgrade, upgrade and reboot to a RHEL8.6 > system for the very first time. > So, the code in PR #983 seems to help here. So far, so good. > After 3 minutes I rebooted that system, and it felt into Kernel panic - not > syncing: VFS: Unable to mount root fs on unknown-block(0,0). No idea what I > did wrong. > > Retest required, when PR has been implemented. Thanks for the testing, Thorsten. I'll try this on our side too and will update on this BZ.
(In reply to IBM Bug Proxy from comment #13) > ------- Comment From thorsten.diehl.com 2022-11-14 05:44 EDT------- > I tested leapp upgrade on s390x SCSI disk with > leapp.noarch 0:0.15.0-100.20221019062411522869.master.6.g14fae66.el7 > leapp-upgrade-el7toel8.noarch > 0:0.17.0-100.20221030153816680418.master.18.g6ec9f0a.el7 > leapp-data-19 > plus manually applied patches from > https://github.com/oamg/leapp-repository/pull/983 > That brought me with leapp preupgrade, upgrade and reboot to a RHEL8.6 > system for the very first time. > So, the code in PR #983 seems to help here. So far, so good. > After 3 minutes I rebooted that system, and it felt into Kernel panic - not > syncing: VFS: Unable to mount root fs on unknown-block(0,0). No idea what I > did wrong. > > Retest required, when PR has been implemented. I retested with the official downstream build and it fixes the issue. IIUC, delivery into RHSM is not planned asynchronously, but Renaud created an article https://access.redhat.com/solutions/6984933 for customers who need early access. Setting Verified:Tested. Version info: leapp.noarch 0.15.0-2.el7_9 @rhel-7-for-system-z-extras-rpms leapp-deps.noarch 0.15.0-2.el7_9 @rhel-7-for-system-z-extras-rpms leapp-upgrade-el7toel8.noarch 0.17.0-2.el7_9 @/leapp-upgrade-el7toel8-0.17.0-2.el7_9.noarch leapp-upgrade-el7toel8-deps.noarch 0.17.0-2.el7_9 @/leapp-upgrade-el7toel8-deps-0.17.0-2.el7_9.noarch python2-leapp.noarch 0.15.0-2.el7_9 @rhel-7-for-system-z-extras-rpms cockpit-leapp.noarch 0.1.6-2.el7_9 rhel-7-for-system-z-extras-rpms leapp-repository.noarch 0.14.0-4.el7_9 rhel-7-for-system-z-extras-rpms leapp-repository-deps.noarch 0.14.0-4.el7_9 rhel-7-for-system-z-extras-rpms leapp-repository-sos-plugin.noarch 0.9.0-4.el7 rhel-7-for-system-z-extras-rpms Used leapp-data: leapp-data-19.tar.gz from official release https://access.redhat.com/articles/3664871#comments
------- Comment From thorsten.diehl.com 2022-11-15 04:34 EDT------- OK, sounds good. Please give me a trigger herein, when version 0.17.0-2 is available on RHSM.
------- Comment From thorsten.diehl.com 2023-01-04 15:38 EDT------- Today I did several successful upgrade tests from RHEL7.9 + latest zStream installed on SCSI LUN in IBM z16 LPAR to RHEL8.8 snapshot, with the following packages from copr: python2-leapp-0.15.0-100.20221216113841714417.master.12.g821358f.el7.noarch leapp-upgrade-el7toel8-0.17.0-100.20230103164306471581.master.48.g0875657.el7.noarch leapp-deps-0.15.0-100.20221216113841714417.master.12.g821358f.el7.noarch leapp-0.15.0-100.20221216113841714417.master.12.g821358f.el7.noarch leapp-upgrade-el7toel8-deps-0.17.0-100.20230103164306471581.master.48.g0875657.el7.noarch leapp-data-19.tar.gz and some tweaks to convince leapp to do an upgrade to RHEL8.8 Everything looks good so far, and I expect a working leapp upgrade shortly after GA of RHEL8.8. Re-test required after GA of RHEL8.8
Petr, currently the ITM is on 20 but IIUC the change will be part of the next brew build right? I set ITM 28 because I think the brew build will be available by ITM 25. Please correct me if I'm wrong. Thanks.
Verified with leapp-upgrade-el7toel8-0.17.0-10.el7_9.noarch that a system on single fcp LUN can be upgraded successfully to RHEL 8.
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 (leapp-repository bug fix update), 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-2023:1228
------- Comment From thorsten.diehl.com 2023-05-23 11:27 EDT------- With RHEL8.8 released, an upgrade from RHEL7.9 to RHEL8.8 with rootfs on SCSI LUN is working now as expected. leapp.noarch 0:0.15.1-1.el7_9 leapp-upgrade-el7toel8.noarch 0:0.18.0-1.el7_9 leapp-data-22.tar.gz Closing this bug.