Bug 1252993 - Anaconda "unknown error" crash after "i accept my fate" (eth0 connection fault)
Summary: Anaconda "unknown error" crash after "i accept my fate" (eth0 connection fault)
Keywords:
Status: CLOSED DUPLICATE of bug 1245960
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-12 16:29 UTC by Andrew Peek
Modified: 2015-08-12 17:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 17:01:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Anaconda log indicating eth0 errors (184.17 KB, text/plain)
2015-08-12 16:29 UTC, Andrew Peek 		no flags Details
View All

Description Andrew Peek 2015-08-12 16:29:57 UTC 
Created attachment 1062099 [details]
Anaconda log indicating eth0 errors

Description of problem: Anaconda GUI crashes with "an unknown error has occurred" after selecting "I accept my fate" when attempting to install F23 Alpha Server from .iso. Exiting into debug console then checking anaconda.log I see problems with activating eth0. Checking network interface status with nmcli, eth0 is disconnected and not assigned an IP address and ifcfg-eth0 config file does not exist. Running "nmcli device connect eth0" connects eth0 and an IP address is assigned indicating DHCP server is working.

I am attempting to install F23 Alpha Server as VM guest on Citrix XenServer 6.5SP1 host. F22 anaconda works without problem as guest on same VM.

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


How reproducible: Reproducible every install attempt.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 David Shea 2015-08-12 17:01:53 UTC 

*** This bug has been marked as a duplicate of bug 1245960 ***
Note You need to log in before you can comment on or make changes to this bug.