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 823646 - Revert delay on kdump bridge
Summary: Revert delay on kdump bridge
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: beta
: ---
Assignee: Joey Boggs
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 812865 817157
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-21 19:14 UTC by Mike Burns
Modified: 2016-04-26 13:48 UTC (History)
11 users (show)

Fixed In Version: ovirt-node-2.5.0-3.el6
Doc Type: Bug Fix
Doc Text:
After kdump was configured with a remote NFS server, the dump file was not created in the NFS directory, so kdump did not work. The link_delay option, which was introduced to fix a prior issue, has now been removed, so kdump on a biosdevname interface with a bridge works as expected.
Clone Of: 812865
Environment:
Last Closed: 2013-02-28 16:31:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0556 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2013-02-28 21:29:06 UTC

Description Mike Burns 2012-05-21 19:14:57 UTC
+++ This bug was initially created as a clone of Bug #812865 +++

Original fix for the below problem was to add Delay=60 to the kdump bridge.  This can be reverted when bug 817157 is fixed.



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.

Comment 1 Mike Burns 2012-05-21 19:18:55 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Without the fix to bug 817157, kdump on a biosdevname interface with a bridge will not function correctly.

Comment 2 RHEL Program Management 2012-07-10 08:22:56 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-11 01:48:46 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 Mike Burns 2012-07-13 20:17:47 UTC
delay on bridge is not needed,  bug 817157 was fixed in 6.3 GA.

Comment 7 Ying Cui 2012-11-05 08:03:21 UTC
Verified this bug on build rhev-hypervisor6-6.4-20121031.0.el6, kdump on a biosdevname interface with a bridge works good after configure the remote nfs server.

Test steps:
 1. Install rhevh on local host
 2. Configure network(biosdevname interface with a bridge)
 3. Scroll down to Kernel Dump, choose setup nfs configuration
 4. Enter the nfs server address, and confirm the input address;
 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.

Test results:
There is dump file named with the dump time in the nfs:/path/var/crash.

So the bug is fixed, change bug status to VERIFIED.

Comment 10 errata-xmlrpc 2013-02-28 16:31:03 UTC
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-2013-0556.html


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