Bug 513021

Summary: Network configuration fails in anaconda 12.3
Product: [Fedora] Fedora Reporter: Clyde E. Kunkel <clydekunkel7734>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, rmaximo, 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: 2009-07-21 17:15:16 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
tty3 of failed anaconda 12.3 auto netwok config
none
tty4 of failed anaconda 12.3 auto network onfig
none
tty4 of failed anaconda 12.3 auto manual networkk config none

Description Clyde E. Kunkel 2009-07-21 17:00:23 UTC
Created attachment 354527 [details]
tty3 of failed anaconda 12.3 auto netwok config

Description of problem:
cannot get network to come up in anaconda 12.3

Version-Release number of selected component (if applicable):
12.3-1.fc12

How reproducible:
each try

Steps to Reproduce:
1. create boot iso from mash/rawhide
2. boot cd and askmethod
3. select auto network (or manual)
  
Actual results:
Error dialogue box pops up: There was an error configuring your network interface.

Expected results:
Working network interface

Additional info:
attaching 3 screen shots: 1) tty3 of failed auto config 2) tty4 of failed autoconfig; and, 3) tty4 of manual config.

Comment 1 Clyde E. Kunkel 2009-07-21 17:01:21 UTC
Created attachment 354528 [details]
tty4 of failed anaconda 12.3 auto network  onfig

Comment 2 Clyde E. Kunkel 2009-07-21 17:02:25 UTC
Created attachment 354529 [details]
tty4 of failed anaconda 12.3 auto manual networkk config

Comment 3 Andy Lindeberg 2009-07-21 17:15:16 UTC

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