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.
Bug 1982099 - [RHEL8] [s39x] KVM "/usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: line 13: /sys/devices/qeth/*/online: No such file or directory"
Summary: [RHEL8] [s39x] KVM "/usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: l...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dracut
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-14 07:51 UTC by Coiby
Modified: 2023-01-14 07:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-14 07:27:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dracutdevs dracut pull 1561 0 None Merged fix(qeth_rules): check the existence of /sys/devices/qeth/*/online beforehand 2022-02-04 09:40:39 UTC

Description Coiby 2021-07-14 07:51:15 UTC
Description of problem:

On s390x KVM machines, the following warning messages would be shown when building kdump initramfs that dump vmcore to a remote fs,

# kdumpctl rebuild
kdump: Rebuilding /boot/initramfs-4.18.0-319.el8.s390xkdump.img
/usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: line 13: /sys/devices/qeth/*/online: No such file or directory
/usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: line 13: /sys/devices/qeth/*/online: No such file or directory

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


How reproducible:

always

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Coiby 2021-07-14 07:54:55 UTC
I've created an upstream PR to fix this issue https://github.com/dracutdevs/dracut/pull/1561.

Comment 2 Jan Stodola 2021-11-22 18:24:08 UTC
It also happens for regular initramfs during the system installation:

05:26:56,270 INF program: Running in chroot '/mnt/sysroot'... dracut -f /boot/initramfs-4.18.0-350.el8.s390x.img 4.18.0-350.el8.s390x
05:27:20,557 INF program: /usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: line 13: /sys/devices/qeth/*/online: No such file or directory
05:27:20,558 INF program: /usr/lib/dracut/modules.d/95qeth_rules/module-setup.sh: line 13: /sys/devices/qeth/*/online: No such file or directory
05:27:20,558 DBG program: Return code: 0

Comment 3 Lukáš Nykrýn 2022-01-04 13:41:43 UTC
https://github.com/redhat-plumbers/dracut-rhel9/pull/16

Comment 5 RHEL Program Management 2023-01-14 07:27:38 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.


Note You need to log in before you can comment on or make changes to this bug.