Description of problem: In a true IPv6 environment, anaconda is not able to configure the network interface properly Version-Release number of selected component (if applicable): Anaconda 13.25 How reproducible: Everytime Steps to Reproduce: 1. Have a IPv6 network in place, where the installation host does not get any IPv4 addressing handed out by a IPv4DHCP server. 2. Start Fedora installation from boot.iso image or vmlinuz and initrd.img already on the host system and start a network installation. 3. When the network interface screen is presented, deactivate IPv4 and fil in IPv6 static addressing scheme 4. Wait until NetworkManager reports network configuration failure. 5. Watch the log info on the other virtual screens. 6. See that NetworkManager although IPv4 was deactivated, still tried to get an IPv4 lease and failed. Actual results: Installation can not be continued Expected results: IPv4 should be ignored, and IPv6 addressing scheme should be configured on the interface. Installation should continue narmally. Additional info: It looks like NetworkManager stops configuring the interface while it can't find IPv4 information.
I've seen this as well and believe it's purely a NM problem, but I'm sure David will know for sure.
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I checked that this works in current anaconda (tested with 15.13). If ipv4 is deactivated in loader UI, it is ignored (dhcp4 is not tried).
This bug is already solved in F14. A related bug is stil present and handled in bug #633815 I consider this bug closed.