Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2140563

Summary: ZFCP systems fail to convert + issue with zipl-switch-to-blscfg [rhel-7.9.z]
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: leapp-repositoryAssignee: Leapp team <leapp-notifications>
Status: CLOSED ERRATA QA Contact: smitterl
Severity: high Docs Contact:
Priority: urgent    
Version: 7.9CC: bugproxy, dhorak, fkrska, held, jomiller, jwboyer, kpfleming, pstodulk, smitterl, tstaudt
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: leapp-repository-0.17.0-10.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-14 13:56:57 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: 1857216    
Attachments:
Description Flags
console_output_after_reboot
none
Output of first "leapp upgrade" command
none
Output of secound "leapp upgrade" command.
none
Output of "leapp preupgrade" command. none

Description Renaud Métrich 2022-11-07 08:55:46 UTC 
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
Comment 3 Petr Stodulka 2022-11-09 09:01:03 UTC 
*** Bug 1969883 has been marked as a duplicate of this bug. ***
Comment 4 IBM Bug Proxy 2022-11-09 09:07:17 UTC 
------- 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 5 IBM Bug Proxy 2022-11-09 09:45:57 UTC 
------- 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
Comment 9 IBM Bug Proxy 2022-11-14 08:11:41 UTC 
Created attachment 1924169 [details]
console_output_after_reboot
Comment 10 IBM Bug Proxy 2022-11-14 08:11:42 UTC 
Created attachment 1924170 [details]
Output of first "leapp upgrade" command
Comment 11 IBM Bug Proxy 2022-11-14 08:11:44 UTC 
Created attachment 1924171 [details]
Output of secound "leapp upgrade" command.
Comment 12 IBM Bug Proxy 2022-11-14 08:11:46 UTC 
Created attachment 1924172 [details]
Output of "leapp preupgrade" command.
Comment 13 IBM Bug Proxy 2022-11-14 10:50:30 UTC 
------- 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.
Comment 15 smitterl 2022-11-14 16:14:41 UTC 
(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.
Comment 17 smitterl 2022-11-15 08:22:31 UTC 
(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 20 IBM Bug Proxy 2022-11-15 09:41:05 UTC 
------- 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 24 IBM Bug Proxy 2023-01-04 20:40:50 UTC 
------- 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
Comment 25 smitterl 2023-01-11 09:43:45 UTC 
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.
Comment 33 smitterl 2023-02-27 13:01:28 UTC 
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.
Comment 35 errata-xmlrpc 2023-03-14 13:56:57 UTC 
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 36 IBM Bug Proxy 2023-05-23 15:31:55 UTC 
------- 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.