Description of problem:

An installation with multipath parameters in the parmfile:

rd.multipath=default
coreos.inst.install_dev=/dev/mapper/mpatha

and hostnames in the parmfile fails.

The installation ends with an emergency shell. Network (IP) is configured, but name resolution is not working. Ping with IP to other system works.

The same installation (with MP parameters) works, if IP addresses are specified instead of hostnames in the parmfile.

It also works with hostnames in the parmfile, if rd.multipath=default is removed and sda is used instead of dev/mapper/mpatha.

It looks like the MP parameter(s) breaks the correct setup of the name resolution during installation. Not sure if it should be there, but there is no /etc/resolv.conf in the booted linux (emergency shell).

Version-Release number of selected component (if applicable):

oc version
Client Version: 4.8.0-0.nightly-s390x-2021-06-18-055818
Server Version: 4.8.0-0.nightly-s390x-2021-06-18-055818
Kubernetes Version: v1.21.0-rc.0+120883f

How reproducible:

Install a node with MP parameters and hostnames in the parmfile.

Steps to Reproduce:
1.
2.
3.

Actual results:

Installation ends in an emergency shell.

Expected results:

Installation process works.

Additional info: