Bug 2015086

Summary:	Booting RHEL 9 on z/VM reports dasdconf.sh Warning: 0.0.0120 is already online, not configuring in journal
Product:	Red Hat Enterprise Linux 9	Reporter:	Jan Pazdziora <jpazdziora>
Component:	s390utils	Assignee:	Dan Horák <dhorak>
Status:	CLOSED WONTFIX	QA Contact:	Vilém Maršík <vmarsik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jpazdziora, rvr
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-18 07:28:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Pazdziora 2021-10-18 11:28:22 UTC

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.

Comment 2 Dan Horák 2021-10-18 12:36:34 UTC

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.

Comment 3 Jan Pazdziora 2021-10-18 12:44:29 UTC

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?

Comment 6 RHEL Program Management 2023-04-18 07:28:28 UTC

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.