Red Hat Bugzilla – Bug 1008841
Kernel panic during kdump when the nfs location is ipv6 address
Last modified: 2014-01-21 14:50:27 EST
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:
Upstream kdump does not support IPv6 targets. IPv6 entries will be marked as invalid in the TUI.
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.
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.
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