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:
Updating kernel in KVM guest shows error message despite finishing correctly.


Version-Release number of selected component (if applicable):
yum-4.2.17-6.el8.noarch
dracut-049-68.git20200211.el8.s390x
kernel-4.18.0-184.el8.s390x

How reproducible:
100%

Preconditions:
1. KVM guest, disks attached through virtio (target vdX)

Steps to Reproduce:
1. Confirm /etc/dasd.conf doesn't exist
2. Make sure another kernel version is available (e.g. add nightly repo)
3. yum update -y kernel

Actual results:
Update finishes correctly but error message shown:
dracut-install: ERROR: installing '/etc/dasd.conf'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.YvVRx5/initramfs -H /etc/dasd.conf


Expected results:
Update finishes correctly.


Additional info:
1. dasd.conf is only required for persistent DASD config, https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/installation_guide/ap-s390info#ap-s390info-Adding_DASDs-Persistently_setting_online
2. workaround is to create an empty file /etc/dasd.conf

Proposed https://github.com/dracutdevs/dracut/pull/771

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (dracut bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1661