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.
Description of problem:
-----------------------
This is an off-shoot from https://bugzilla.redhat.com/show_bug.cgi?id=1680049
where installation of RHEL8-beta fails on IBM z Systems with repeated messages like
"dracut-initqueue[950]: Warning: dracut-initqueue timeout - starting timeout scripts"
This is a consequence because of a new naming scheme for s390x network devices introduced in https://github.com/systemd/systemd/commit/0037a669ac9a2bbedccdb2f483111351e8ff4659
Please, add some code into dracut that would automatically convert the rhel7 interface names to the short variants in rhel8 on the fly.
How reproducible:
-----------------
At every installation attempt using the original network interface naming scheme, e.g. enccw0.0.a700
Steps to Reproduce:
-------------------
1. Attempt to install RHEL8-beta on a dedicated s390x LPAR using generic.prm file like
ro ramdisk_size=40000 cio_ignore=all,!condev rd.znet=qeth,0.0.a700,0.0.a701,0.0.a702,layer2=1,portno=0 ip=<IP1>::<IP2:Mask>:zll0009:enccw0.0.a700:none rd.dasd=0.0.A904 inst.repo=nfs:nfsvers=3:<repo_server_IP>:/inst/zLinux/rhel-server-8-beta-s390x-dvd
Actual results:
---------------
The installation does not complete, fails with "dracut-initqueue[950]: Warning: dracut-initqueue timeout - starting timeout scripts"
The initial suspicion is on iSCSI as the last messages before the repeated dracut-initqueue timeouts came from iSCSI
Expected results:
-----------------
Normally completed installation
To me, this looks like a really bad idea. I don't believe that dracut (or any other software) should ever try to fix user errors. I really don't want to add a patch that does "well this looks like a configuration from rhel7 so let's change it to the equivalent of rhel8".
In the past, we thought about building udev-builtin-net_id from rhel7 as a separate library and giving the user an option to opt-in into the old behaviour, which would partly solve this issue.
Per the reasoning in comment 3, I am closing this bug as WONTFIX. Please use the contents of the following knowledgebase article in order to correct the applicable configurations in the event that this issue is encountered.