DescriptionPrashanth Sundararaman
2021-12-14 14:58:41 UTC
+++ This bug was initially created as a clone of Bug #2031637 +++
Description of problem:
1. zVM environment OCP 4.10 on Z cluster installation fails for OCP 4.10 4.10.0-0.nightly-s390x-2021-12-10-233457 build with RHCOS 410.84.202112091602-0 build: fails to install with "executing lszdev on /dev/dasda; No such file or directory (os error 2)" message.
2. Here are the error messages received for each bootstrap, master (control), worker (compute) node when attempting to boot and install RHCOS 410.84.202112091602-0:
12/12/21 23:59:06 [ 13.648751] coreos-installer-service[1229]: coreos-installer install /dev/dasda --ignition-url http://bastion.pok-25.ocptest.pok.stglabs.i
12/12/21 23:59:06 [ 13.747032] coreos-installer-service[1229]: Error: getting sector size of /dev/dasda
12/12/21 23:59:06 [ 13.747120] coreos-installer-service[1229]: Caused by:
12/12/21 23:59:06 [ 13.747140] coreos-installer-service[1229]: 0: executing lszdev on /dev/dasda
12/12/21 23:59:06 [ 13.747172] coreos-installer-service[1229]: 1: No such file or directory (os error 2)
12/12/21 23:59:06 [[0;1;31mFAILED[0m] Failed to start CoreOS Installer.
3. Inspection of the /usr/sbin directory in maintenance mode indicates that, as expected by the above messages, the /usr/sbin/lszdev file is not present.
Version-Release number of selected component (if applicable):
1. OCP 4.10 nightly build 4.10.0-0.nightly-s390x-2021-12-10-233457
2. RHCOS build 410.84.202112091602-0
How reproducible:
Consistently reproducible.
Steps to Reproduce:
1. Attempt to install OCP 4.10 nightly build 4.10.0-0.nightly-s390x-2021-12-10-233457 with RHCOS 410.84.202112091602-0.
Actual results:
Bootstrap, master (control plane), and worker (compute) nodes all fail to boot and install RHCOS wuth the same error message as contained in the first section of this bugzilla.
Expected results:
All of the bootstrap, master (control plane), and worker (compute) nodes should all successfully install the RHCOS build.
Additional info:
Thank you.
--- Additional comment from Prashanth Sundararaman on 2021-12-13 19:13:45 UTC ---
Looks like lszdev is not in s390utils-core. According to this comment a while ago: https://github.com/coreos/fedora-coreos-config/pull/756#issuecomment-754699901 Dan Horak did move fdasd and lszdev to s390utils-core, but looks like it is only present in version 2.16 which is part of RHEL 8.5
Dan,
Can this change be backported to 8.4 s390utils-core to fix this issue?
Thanks
Prashanth
--- Additional comment from Prashanth Sundararaman on 2021-12-13 19:33:37 UTC ---
rhcos uses the 8.4 EUS rpms to build: http://rhsm-pulp.corp.redhat.com/content/eus/rhel8/8.4/s390x/baseos/os/Packages/s/ and they have an older version of s390utils-core which does not contain fdasd and lszdev
--- Additional comment from Dan Li on 2021-12-13 23:32:36 UTC ---
Setting a needinfo for Dan per Comment 1
--- Additional comment from on 2021-12-14 06:53:21 UTC ---
Folks,
FYI and for OCP on Z support documentation purposes: OCP 4.10 on Z RHCOS build 410.84.202112132002-0 fails with the same issue.
Thank you,
Kyle
--- Additional comment from Dan Horák on 2021-12-14 09:43:45 UTC ---
(In reply to Prashanth Sundararaman from comment #1)
> Looks like lszdev is not in s390utils-core. According to this comment a
> while ago:
> https://github.com/coreos/fedora-coreos-config/pull/756#issuecomment-
> 754699901 Dan Horak did move fdasd and lszdev to s390utils-core, but looks
> like it is only present in version 2.16 which is part of RHEL 8.5
>
> Dan,
>
> Can this change be backported to 8.4 s390utils-core to fix this issue?
yes, that shouldn't be a big issue. Could you somehow clone this bug into a RHEL bug for s390utils? I will then clone it further for the 8.4.0.z zstream.