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:
In RHEL-9.1 image on Hyper-V/Azure, after reboot, the kdump reports an error message in 'systemctl status kdump':
kdumpctl[1287]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite
* The kdump service works well. Not see feature impact.
* Not see it in RHEL-8.7.
* Not see it in an earlier RHEL-9.1(e.g. RHEL-9.1.0-20220529.0, kernel-5.14.0-100.el9.x86_64, kexec-tools-2.0.24-1.el9.x86_64 )
Version-Release number of selected component (if applicable):
RHEL-9.1.0-20220720.3
kernel-5.14.0-131.el9.x86_64
kexec-tools-2.0.24-4.el9.x86_64/kexec-tools-2.0.24-5.el9.x86_64
dracut-057-6.git20220718.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Boot a RHEL-9.1 VM on Azure
2. Reboot the VM
3. systemctl status kdump
Actual results:
[root@wala9test107210916-vm1 ~]# systemctl status kdump
● kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled)
Active: active (exited) since Thu 2022-07-21 05:51:31 EDT; 29s ago
Process: 1107 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS)
Main PID: 1107 (code=exited, status=0/SUCCESS)
CPU: 1.265s
Jul 21 05:51:27 wala9test107210916-vm1 systemd[1]: Starting Crash recovery kernel arming...
Jul 21 05:51:28 wala9test107210916-vm1 kdumpctl[1287]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite
Jul 21 05:51:29 wala9test107210916-vm1 kdumpctl[1375]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite
Jul 21 05:51:31 wala9test107210916-vm1 kdumpctl[1119]: kdump: kexec: loaded kdump kernel
Jul 21 05:51:31 wala9test107210916-vm1 kdumpctl[1119]: kdump: Starting kdump: [OK]
Jul 21 05:51:31 wala9test107210916-vm1 systemd[1]: Finished Crash recovery kernel arming.
Additional info:
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-2022:8379
Description of problem: In RHEL-9.1 image on Hyper-V/Azure, after reboot, the kdump reports an error message in 'systemctl status kdump': kdumpctl[1287]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite * The kdump service works well. Not see feature impact. * Not see it in RHEL-8.7. * Not see it in an earlier RHEL-9.1(e.g. RHEL-9.1.0-20220529.0, kernel-5.14.0-100.el9.x86_64, kexec-tools-2.0.24-1.el9.x86_64 ) Version-Release number of selected component (if applicable): RHEL-9.1.0-20220720.3 kernel-5.14.0-131.el9.x86_64 kexec-tools-2.0.24-4.el9.x86_64/kexec-tools-2.0.24-5.el9.x86_64 dracut-057-6.git20220718.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Boot a RHEL-9.1 VM on Azure 2. Reboot the VM 3. systemctl status kdump Actual results: [root@wala9test107210916-vm1 ~]# systemctl status kdump ● kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: enabled) Active: active (exited) since Thu 2022-07-21 05:51:31 EDT; 29s ago Process: 1107 ExecStart=/usr/bin/kdumpctl start (code=exited, status=0/SUCCESS) Main PID: 1107 (code=exited, status=0/SUCCESS) CPU: 1.265s Jul 21 05:51:27 wala9test107210916-vm1 systemd[1]: Starting Crash recovery kernel arming... Jul 21 05:51:28 wala9test107210916-vm1 kdumpctl[1287]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite Jul 21 05:51:29 wala9test107210916-vm1 kdumpctl[1375]: ERROR: src/skipcpio/skipcpio.c:191:main(): fwrite Jul 21 05:51:31 wala9test107210916-vm1 kdumpctl[1119]: kdump: kexec: loaded kdump kernel Jul 21 05:51:31 wala9test107210916-vm1 kdumpctl[1119]: kdump: Starting kdump: [OK] Jul 21 05:51:31 wala9test107210916-vm1 systemd[1]: Finished Crash recovery kernel arming. Additional info: