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.