Bug 626023

Summary: anaconda fails to configure network on fixed IP networks
Product: Red Hat Enterprise Linux 6 Reporter: Rich Johnson <richard.johnson>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: andriusb, chas.horvath, jparadis, robert.evans, rvykydal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-23 08:27:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda boot command
none
Attempt to use dhclient
none
NIC activation failure none

Description Rich Johnson 2010-08-21 14:24:13 UTC 
Fails to configure network on fixed IP networks.  
Loader insists on invoking dhclient despite IP configuration on command line

Version-Release number of selected component (if applicable):
RHEL6.0-20100811.2-Server-x86_64-DVD1.iso
anaconda-13.21.74-1.el6
kernel-2.6.32-63.el6
NetworkManager-0.8.1-5.el6

How reproducible:
Boot DVD with fixed IP and nfs: kickstart address  on a network w/o DHCP

Steps to Reproduce:
1.
2.
3.
  
Actual results:
  -" There was an error configuring your network interface"

Expected results:
  - Network configured, Installation proceeds


Additional info:
Regression from RHEL6.0-20100805-Server-x86_64-DVD1.iso
See attached screen shots
Comment 2 Rich Johnson 2010-08-21 14:33:57 UTC 
Created attachment 440122 [details]
anaconda boot command
Comment 3 Rich Johnson 2010-08-21 14:39:22 UTC 
Created attachment 440126 [details]
Attempt to use dhclient
Comment 4 Rich Johnson 2010-08-21 14:41:18 UTC 
Created attachment 440128 [details]
NIC activation failure
Comment 5 Radek Vykydal 2010-08-23 08:27:15 UTC 
This should be fixed in Snapshot #12.

*** This bug has been marked as a duplicate of bug 623937 ***