Bug 849360 - traceback at Continue after first plug of network cable: No such file or directory /etc/sysconfig/network-scripts/ifcfg-<port>
Summary: traceback at Continue after first plug of network cable: No such file or dire...
Keywords:
Status: CLOSED DUPLICATE of bug 849012
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-18 19:04 UTC by John Reiser
Modified: 2013-01-10 06:53 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-18 20:22:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda-tb-* traceback and debuginfo (421.53 KB, text/plain)
2012-08-18 19:04 UTC, John Reiser
no flags Details

Description John Reiser 2012-08-18 19:04:18 UTC
Created attachment 605372 [details]
anaconda-tb-* traceback and debuginfo

Description of problem: Installer aborts with error and traceback when user Continues after plugging in only network cable.


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

How reproducible: every time (2 of 2 so far)


Steps to Reproduce:
1. establish isolated machine: unplug all network cables, turn off Wifi, etc.
2. boot Fedora-18-Alpha-TC3 netinst.iso (i686) from DVD, accept default kernel boot (Test this media & install/update Fedora), default Language (English US), installer Fate.
3. wait for request "We'll need network access ..." showing unplugged cable.
4. plug in network cable, wait 3 seconds to be recognized, 2 seconds for DHCP.
5. Click Continue.
  
Actual results: unexpected error traceback: No such file or directory: /etc/sysconfig/network-scripts/ifcfg-<port_name>


Expected results: Proceed with install.


Additional info:

Comment 1 Jesse Keating 2012-08-18 20:22:53 UTC

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


Note You need to log in before you can comment on or make changes to this bug.