Bug 328931

Summary: anaconda writes IPV6ADDR=dhcp in ifcfg-eth<whatever>
Product: [Fedora] Fedora Reporter: Bill Nottingham <notting>
Component: anacondaAssignee: David Cantrell <dcantrell>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-23 17:05:19 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235703    

Description Bill Nottingham 2007-10-12 00:00:29 EDT
Description of problem:

That's not valid. What are you intending by such a configuration?

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

Comment 1 Bill Nottingham 2007-10-12 00:01:39 EDT
Poking at the anaconda source, I see:

loader.c:648:        loaderData->ipv6 = strdup("dhcp");
loader.c:1272:                        loaderData->ipv6 = strdup("dhcpv6");

Presumably that's the source, although one of those lines probably needs fixed.
Comment 2 Bill Nottingham 2007-10-12 00:38:55 EDT
*** Bug 328921 has been marked as a duplicate of this bug. ***
Comment 3 David Cantrell 2007-10-23 17:05:19 EDT
The internal Network object in anaconda does not directly map down to ifcfg-*
settings.  At one point it did, so I added support to write out correct IPV6
values based on what we collected from the user.