Bug 849467

Summary: f18 tc3 anaconda entering and exit network configuration produces "an unknown error has occurred"
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: g.kaviyarasu, jonathan, 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: 2012-08-20 08:44:46 UTC Type: Bug
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
screenshot of the error
none
screenshot partial error log
none
screenshot partial error log II none

Description Reartes Guillermo 2012-08-19 17:51:46 UTC
Created attachment 605524 [details]
screenshot of the error

Description of problem:

When testing F18 tc3, if i enter "network configuration" and exit (nothing was 
changed), anaconda emits: "an unknown error has occurred" -> ""
Version-Release number of selected component (if applicable):

Due to using a kvm guest and i could not launch a terminal from the anaconda-ui, no logs for now. But i will attach some screenshots.

How reproducible:
allways. 


Steps to Reproduce:
1. boot 
2. enter network configuration
3. exit
  
Actual results:
anaconda restarts the system

Expected results:
no error

Additional info:
i happened also with prior anaconda test images.

Comment 1 Reartes Guillermo 2012-08-19 17:52:28 UTC
Created attachment 605525 [details]
screenshot partial error log

Comment 2 Reartes Guillermo 2012-08-19 17:52:58 UTC
Created attachment 605526 [details]
screenshot partial error log II

Comment 3 Radek Vykydal 2012-08-20 08:44:46 UTC

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