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:
While installing a new kernel with "yum install" or "yum update", there are some "Broken Pipe" warnings from gzip and sort while dracut runs. They are likely harmless, since the kernel works afterwards anyway, but still this can be confusing for the user and should be avoided
Version-Release number of selected component (if applicable):
dracut-049-95.git20200804.el8.s390x
(also happens with dracut-049-100, but that causes other trouble, see BZ 1904642)
How reproducible:
100%
Steps to Reproduce:
1. Install a new kernel with "yum install" or "yum update"
Actual results:
gzip: stdout: Broken pipe
gzip: stdout: Broken pipe
sort: write failed: 'standard output': Broken pipe
sort: write error
Expected results:
No scary error messages.
Additional info:
The problem seems only to happen during installation with yum. If I re-generate an initramfs manually by calling dracut directly, the error messages do not occur!
I've also added some debug echo statements to /usr/bin/dracut to locate the origin of the error messages, and if I've got that right, they seem to be generated by this part of the script:
if (( maxloglvl >= 5 )) && (( verbosity_mod_l >= 0 )); then
if [[ $allowlocal ]]; then
"$dracutbasedir/lsinitrd.sh" "${DRACUT_TMPDIR}/initramfs.img"| ddebug
else
lsinitrd "${DRACUT_TMPDIR}/initramfs.img"| ddebug
fi
fi