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 1008841 - Kernel panic during kdump when the nfs location is ipv6 address
Summary: Kernel panic during kdump when the nfs location is ipv6 address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ryan Barry
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1037958
TreeView+ depends on / blocked
 
Reported: 2013-09-17 07:29 UTC by wanghui
Modified: 2014-01-21 19:50 UTC (History)
15 users (show)

Fixed In Version: ovirt-node-3.0.1-4.el6
Doc Type: Bug Fix
Doc Text:
The hypervisor allowed IPv6 addresses to be entered as kdump targets, but the kdump service does not support IPv6. Now, the hypervisor marks IPv6 addresses as kdump targets as invalid.
Clone Of:
: 1037958 (view as bug list)
Environment:
Last Closed: 2014-01-21 19:50:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 0 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-22 00:14:30 UTC
oVirt gerrit 20124 0 None None None Never

Description wanghui 2013-09-17 07:29:39 UTC 
Description of problem:
Can't mount nfs storage when the server address is ipv6. It also miss validation for the nfs location. And

Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.5-20130725.0.auto1831.el6.iso

How reproducible:
100%

Steps to Reproduce:
1. Clean install rhev-h 6.5 and enable network.
2. Set nfs location with ipv6 address.
3. Drop to shell and cat the kdump.conf file.
4. Drop to shell and run #echo c >/proc/sysrq-trigger

Actual results:
1. After step2, it will report "All changes were applied successfully.".
2. After step3, it persist the configuration.
3. After step4, it will kernel panic.

Expected results:
1. After step4, kdump can run successfully. And there should have dump file in the ipv6 address server.

Additional info:
Comment 3 Ryan Barry 2013-10-11 17:35:06 UTC 
Upstream kdump does not support IPv6 targets. IPv6 entries will be marked as invalid in the TUI.
Comment 5 wanghui 2013-10-21 11:55:31 UTC 
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6.noarch

Test steps:
1. Clean install rhev-h 6.5 and enable network.
2. Set nfs location with ipv6 address.


Test results:
1. After step2, it will give a prompt and not accept the ipv6 address.

According comment#3, the bug is fixed in rhev-hypervisor6-6.5-20131017.0.iso. So change the bug's status from ON_QA to VERIFIED.
Comment 7 Cheryn Tan 2013-11-08 00:25:44 UTC 
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.
Comment 9 errata-xmlrpc 2014-01-21 19:50:27 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-2014-0033.html
Note You need to log in before you can comment on or make changes to this bug.