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 577710[details]
KdumpDoesntWorkPictures
Description of problem:
Kdump doesn't work after configure the remote nfs server
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.3-20120411.1
How reproducible:
100%
Steps to Reproduce:
1. Install rhevh on local host
2. Configure network
3. Scroll down to Kernel Dump, choose setup nfs configuration
4. Enter the nfs server address, and confirm the input address;[attachment RemoteNFS.png]
5. Change to shell mode, and input "echo c > /proc/sysrq-trigger", to make the system coredump;
6. After the system reboot, check the dump file on the remote nfs input before.
Actual results:
There is folder nfs:/path/var/crash in the nfs directory.
But there is no dump file named with the dump time.
[attachment NoDumpFile.png]
Expected results:
There is dump file named with the dump time in the nfs:/path/var/crash.
Additional info:
This a regression test.
(In reply to comment #3)
> ps: The kdump works well in the last build:
> rhev-hypervisor6-6.3-20120409.0.el6_2.
Sorry there is a mistake about the name of the last build.
It should be rhev-hypervisor6-6.3-20120330.0.el6.
(In reply to comment #4)
> ps: The kdump works well in the last build:
> rhev-hypervisor6-6.3-20120409.0.el6_2.
Sorry there is a mistake about the name of the last build.
It should be rhev-hypervisor6-6.3-20120330.0.el6.
Created attachment 578249[details]
kdump log
The attachment Kdump6.3 is the log grabbed through serial console on two rhevh versions.
I have tried the tests on the same machine with the same nfs storage path, but the different rhevh version.
The kdump works well on the last rhevh version: 6.3-20120330.0.el6.
The kdump couldn't get a DHCP address retRestarting system on the rhevh 6.3-20120411.1; so there is no the dump file named with host-name and dump time on the nfs storage.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2012-0741.html
Created attachment 577710 [details] KdumpDoesntWorkPictures Description of problem: Kdump doesn't work after configure the remote nfs server Version-Release number of selected component (if applicable): rhev-hypervisor6-6.3-20120411.1 How reproducible: 100% Steps to Reproduce: 1. Install rhevh on local host 2. Configure network 3. Scroll down to Kernel Dump, choose setup nfs configuration 4. Enter the nfs server address, and confirm the input address;[attachment RemoteNFS.png] 5. Change to shell mode, and input "echo c > /proc/sysrq-trigger", to make the system coredump; 6. After the system reboot, check the dump file on the remote nfs input before. Actual results: There is folder nfs:/path/var/crash in the nfs directory. But there is no dump file named with the dump time. [attachment NoDumpFile.png] Expected results: There is dump file named with the dump time in the nfs:/path/var/crash. Additional info: This a regression test.