Bug 529636 - [NetApp 5.5 bug] mkinitrd does not support IPv6 configuration
Summary: [NetApp 5.5 bug] mkinitrd does not support IPv6 configuration
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd
Version: 5.4
Hardware: All
OS: Linux
high
high
Target Milestone: alpha
: 5.5
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 533941 5.5_Known-Issues
TreeView+ depends on / blocked
 
Reported: 2009-10-19 09:19 UTC by Tanvi
Modified: 2010-03-19 05:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
iSCSI root devices do not function correctly if used over an IPv6 network connection. While the installation will appear to succeed, the system will fail to find the root filesystem during the first boot. (BZ#529636)
Clone Of:
Environment:
Last Closed: 2009-11-30 23:22:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tanvi 2009-10-19 09:19:42 UTC
Description of problem:
I want to setup a REL5.4 host where root is on an iscsi device and it uses IPv6 n/w to access iscsi target. Presently this configuration does not work. There are two ways to configure this
1. Install through IPv6 n/w
2. Install though IPv4 n/w, then enable IPv6 n/w and recreate initrd image

None of the above options works. When installed through IPv6 n/w (see bugzilla 525054), the installation happens properly but after first reboot the host does not boot up due to unavailability of network.
The mkinitrd script does not take care of IPv6 IP configuration and the IPv6 modules does not get included in the initrd.

Version-Release number of selected component (if applicable):
mkinitrd-5.1.19.6-54

How reproducible:
Always

Steps to Reproduce:
1.Configure the host to use IPv6 n/w to access iscsi target
2.Recreate the initrd image using mkinitrd script
3.Reboot the host, host will hang during boot up due to network unavailability
  
Actual results:
mkinitrd does not collect information related to IPv6 configuration and in a scenario where root is on iscsi device the host does not boot.

Expected results:
when root is on iscsi device and IPv6 n/w is being used, the host should be able to boot up.

Comment 2 Denise Dumas 2009-10-28 13:22:12 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Do not use an iscsi root  device if you
locate the device through an IPv6 network. Although the installation will succeed, the subsequent reboot will fail to find /.

Comment 3 Andrius Benokraitis 2009-11-24 19:47:30 UTC
Ryan - this release note needs to be added for RHEL 5.5 and all subsequent release notes. Let me know!

Comment 4 Andrius Benokraitis 2009-11-24 19:50:58 UTC
Note to NetApp: This is a huge amount a work, and we don't foresee this happening anytime soon in RHEL 5, so therefore this will be closed. All effort for this request should be made in RHEL 6.

Comment 5 Ryan Lerch 2009-11-30 04:34:36 UTC
Andrius:

Thanks!

I have added this one to the Known Issues Tracker for 5.5, so it will be included in the Technical Notes for 5.5 and onwards.

cheers,
ryanlerch

Comment 6 Andrius Benokraitis 2009-11-30 23:23:26 UTC
Closing, since known issue has been logged.

Comment 7 Ryan Lerch 2010-03-19 00:10:53 UTC
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1,2 +1 @@
-Do not use an iscsi root  device if you
+iSCSI root devices do not function correctly if used over an IPv6 network connection. While the installation will appear to succeed, the system will fail to find the root filesystem during the first boot. (BZ#529636)-locate the device through an IPv6 network. Although the installation will succeed, the subsequent reboot will fail to find /.


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