Bug 691664

Summary: IPv6 boot option not honoured
Product: [Fedora] Fedora Reporter: A.J. Werkman <aj.werkman>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: medium    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-30 09:02:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Anaconda.log
none
Syslog none

Description A.J. Werkman 2011-03-29 08:20:14 UTC 
Description of problem:
The anaconda boot option "ipv6=" does not configure the network interface with a static ipv6 address.

Version-Release number of selected component (if applicable):
Anaconda 15.25

How reproducible:
Everytime

Steps to Reproduce:
1. Start an installation with "nopiv4 ipv6=<ipv6 address> gateway=<ipv6 address> dns=<ipv6 address>" on the commandline
2. Proceed in the first fase of installation and goto the text network UI. See that IPv4 is not checked DNS address and gateway address are filled in but IPv6 address and prefix are not filled in.
  
Actual results:
IPv6 address from the boot options is not passed on to anaconda.

Expected results:
IPv6 address is configured and anaconda is able to copy packages over the network.

Additional info:
Comment 1 Radek Vykydal 2011-03-29 15:19:16 UTC 
Can you please attach /tmp/anaconda.log and /tmp/syslog?
Comment 2 A.J. Werkman 2011-03-29 19:50:29 UTC 
Created attachment 488549 [details]
Anaconda.log
Comment 3 A.J. Werkman 2011-03-29 19:51:28 UTC 
Created attachment 488550 [details]
Syslog
Comment 4 A.J. Werkman 2011-03-29 19:54:57 UTC 
Although DNS server and IPv6 default gateway end up correctly in ifcfg-pci10p1, they don't show up in resolv.conf and in the routing table respectivly.

Is this also related to the cause of this bug?
Comment 5 Radek Vykydal 2011-03-30 09:02:22 UTC 
20:19:39,311 INFO loader: kernel command line:
20:19:39,311 INFO loader:     gateway=2001:838:3ab:1::1
20:19:39,311 INFO loader:     noipv4
20:19:39,311 INFO loader:     selinux=0
20:19:39,311 INFO loader:     dns=2001:838:3ab:1::1
20:19:39,312 INFO loader:     repo=http://thlin.digifarma.nl/fedora/releases/test/15/x86_64/os
20:19:39,312 INFO loader:     nomodeset
20:19:39,312 INFO loader:     ipv6=2001:838:3ab:1::215/64

ip address should be set without the prefix:
ipv6=2001:838:3ab:1::215