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.
Created attachment 487187[details]
screen output of kdump fail to work
Description of problem:
Configure kdump location properly and then trigger system crash, it does not send vmcore file to remote nfs server or send incomplete vmcore file to ssh location.
[root@localhost ~]# cat /etc/kdump.conf
default reboot
net 10.66.8.216:/var/crash
[root@localhost ~]# service kdump status
Kdump is operational
[root@localhost ~]# echo c > /proc/sysrq-trigger
Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-10
How reproducible:
Always.
Steps to Reproduce:
1. setenforce 0 as bug 654565 exist.
2. configure kdump nfs or ssh location.
3. check kdump service is running
# service kdump status
Kdump is operational
3. make system crash: echo c > /proc/sysrq-trigger
Actual results:
it does not send vmcore file to remote nfs server or send incomplete vmcore file to ssh location.
Expect Results:
A complete vmcore file is generated at remote location.
Additional info:
1. Attach screen output via serial console.
2. It is regression as it's not happened on 6.1-9, but ovirt-config-kdump file is the same.
That looks like a kdump regression, not RHEV-H specific, can it be reproduced with plain RHEL 6.1?
Relevant package manifest diff 6.1-9 vs 6.1-10 is:
-kernel-2.6.32-122.el6
+kernel-2.6.32-124.el6
-kexec-tools-2.0.0-169.el6
+kexec-tools-2.0.0-173.el6
(In reply to comment #3)
> That looks like a kdump regression, not RHEV-H specific, can it be reproduced
> with plain RHEL 6.1?
It should be kexec-tools regression issue, test it on RHEL6.0 but with new kernel:
kernel-2.6.32-125.el6
kdump work on kexec-tools-2.0.0-169.el6
kdump fail on kexec-tools-2.0.0-174.el6