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:

Booting RHEL 9 on z/VM reports

  dasdconf.sh Warning: 0.0.0120 is already online, not configuring

twice in journal. This message is not present when booting on KVM guest.

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

s390utils-core-2.17.0-4.el9.s390x

How reproducible:

Deterministic.

Steps to Reproduce:
1. journalctl -l | grep -i 'dasdconf.sh.*warning'

Actual results:

Oct 18 06:59:57 machine.example.com unknown: dasdconf.sh Warning: 0.0.0120 is already online, not configuring
Oct 18 06:59:59 machine.example.com unknown: dasdconf.sh Warning: 0.0.0120 is already online, not configuring

Expected results:

No warnings.

Additional info:

The value 0.0.0120 seems to be coming from

# cat /etc/dasd.conf 
0.0.0120

and it is not present on the s390x KVM guest.

The "warning" part of the message and the fact that the message gets produced twice indicates that something is not configured quite smoothly.

This is not a new issue in RHEL-9 and I believe it's produced for devices that are part of the / and are initialized first by dracut early during the boot and then by the device_cio_free service, because they are also listed in /etc/dasd.conf. The second initialization is a no-op in fact.

https://fedorapeople.org/cgit/sharkcz/public_git/utils.git/tree/dasdconf.sh#n53 is the source of the message

A proper fix will require the installer and the device initialization to be migrated off the legacy RH scripts and to be moved to the modern "zdev" style, which hasn't happened yet, please see bug #1572568 and related.

Thanks Dan for the prompt explanation. That bug 1572568, is it realistic to get it addressed in RHEL 8, at this point? Wouldn't focusing that work to RHEL 9 (and only later perhaps backporting to RHEL 8) give it better chance of making the capacity cut?

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.