Bug 432035

Created attachment 294363 [details]
/tmp/anaconda.log

It seems that this only presents itself in text mode.  When installing from
graphical mode (normal, vnc), everything seems to be ok.

Created attachment 294396 [details]
updates image that solves the bug. hopefully.

just start text install with the updates argument pointing to this image.

Fixed in anaconda-11.1.2.99-1 and later.

Created attachment 294542 [details]
Additional changes.

FYI,  Tested in my environment and All seems well.  Made an additional tweak to
the code that handles the ip/prefix versus only ip case better.  The updates
image for that is attached.
Recommend testing with current anaconda and this updates image.

Verified with anaconda-11.1.2.99-1 / RHEL5.2-Server-20080211.nightly

----- Additional Comments From gongjie.com  2008-05-06 05:26 EDT
-------
Tested with RHEL5.2 Snapshot7.  The problem was not fixed. 


This event sent from IssueTracker by jkachuck 
 issue 140830

----- Additional Comments From vinaysridhar.com  2008-05-06 05:36
EDT -------
RedHat,
From the above comments, it appears that anaconda version 11.1.2.99 has
fixed
the issue.
However, RHEL5.2 snap7 has version 11.1.2.113..which is a higher version
and the
bug reappears. 


This event sent from IssueTracker by jkachuck 
 issue 140830

The reason the fix does not work for the scenario in issue 140830 is that
your /etc/sysconfig/network contains a line:
NETWORKING_IPV6=no

If you follow the reproducer from comment #0 on a box with one network card,
everything is set up correctly, i.e. ifcfg-eth0 contains correct IPV6ADDR
value and /etc/sysconfig/network contains line: NETWORKING_IPV6=yes

As long as you try to reproduce it on a box with multiple network cards
(issue 140830 references a ppc box with 4 NICs, sets IPv6 address for eth3),
you get the correct ifcfg-eth? (ifcfg-eth3 in this case), but your
/etc/sysconfig/network contains:
NETWORKING_IPV6=no

I'm not quite sure why that happens, changing the value to yes solves
the problem though.

OK, so the IPv6 setup on a box with multiple nics works fine as long as you
set the custom IPv6 address for eth0 (ifcfg-eth0 is OK, NETWORKING_IPV6=yes).

If you set up custom IPv6 address for anything else (eth1 and above), you
end up with NETWORKING_IPV6=no.

Created attachment 304664 [details]
the patch so I dont forget.

Per sly, I cloned this BZ as 445394 for 5.3 and am setting this back to
VERIFIED. Also set the release note flag.  
Suggested Release Note text: 

Installation using an IPv6 setup works only when setting the custom IPv6 address
for eth0 (ifcfg-eth0 is OK, NETWORKING_IPV6=yes). Other NICs result in
configurations in which NETWORKING_IPV6=no.  

thanks Denise, revising release note as:

<quote>
To perform an installation using an IPv6 setup, you need to set the custom IPv6
address for eth0. In doing so, ifcfg-eth0 will be set to OK, and NETWORKING_IPV6
will be automatically set to YES (for eth0). For other NICs, NETWORKING_IPV6
will be set to NO.
</quote>

please advise if correct, and i will add to the RHEl5.2 release notes updates.
thanks!

(In reply to comment #17)
> <quote>
> To perform an installation using an IPv6 setup, you need to set the custom
> IPv6 address for eth0. In doing so, ifcfg-eth0 will be set to OK, and 
> NETWORKING_IPV6
> will be automatically set to YES (for eth0). For other NICs, NETWORKING_IPV6
> will be set to NO.
> </quote>

I think following note would be more appropriate:

<quote>
Installation on a system with multiple network interfaces and manually specified
IPv6 address may result into partially broken networking setup and your IPv6
settings may not be visible on the installed system. To workaround this problem,
change NETWORKING_IPV6=no in /etc/sysconfig/network to NETWORKING_IPV6=yes and
restart your networking setup by running: service network restart
</quote>

thanks Milan, revising as:

<quote>
Installing Red Hat Enterprise Linux 5.2 on a system with multiple network
interfaces and manually specified IPv6 addresses may result in a partially
incorrect networking setup. When this occurs, your IPv6 settings will not be
visible on the installed system.
		
To work around this, set NETWORKING_IPV6 to yes in /etc/sysconfig/network. Then,
restart your network connection using the command service network restart.
</quote>

please advise if any further revisions are required. thanks!

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0397.html

Tracking this bug for the Red Hat Enterprise Linux 5.3 Release Notes.

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.

------- Comment From gongjie.com 2008-11-04 03:18 EDT-------
Test this problem on RHEL5.3 Beta.  This problem is not fix at all.  The
original problem is described clearly in comment #29 and comment #30.

------- Comment From gongjie.com 2008-11-04 04:08 EDT-------
To verify and reproduce this bug,  we do NOT need IPv6 network
environment.  We do NOT need IPv6 network communication in the RHEL5
installing stage.  This bug is talking about the IPv6 network
configuration did not take effect after installation.  The RHEL5 itself,
is installed via IPv4 network.


This event sent from IssueTracker by jkachuck 
 issue 140830