Bug 1011536

Summary: exception in anaconda when trying a network installation of RHEL-7.0-20130923.n.0
Product: Red Hat Enterprise Linux 7 Reporter: Mike FABIAN <mfabian>
Component: pykickstartAssignee: Chris Lumens <clumens>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mfabian, vpodzime
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-24 14:10:35 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:
Bug Depends On: 1004889    
Bug Blocks:    
Attachments:
Description Flags
tmp-log.tar.gz
none
an-unknown-error-has-occured-python-backtrace.png
none
anaconda-tb-dL1koU none

Description Mike FABIAN 2013-09-24 13:45:40 UTC 
Created attachment 802251 [details]
tmp-log.tar.gz

I’m trying to install RHEL-7.0-20130923.n.0. I use

http://download.devel.redhat.com/composes/nightly/RHEL-7.0-20130923.n.0/compose/Workstation/x86_64/os/images/boot.iso

to boot and then enter

http://download.devel.redhat.com/composes/nightly/RHEL-7.0-20130923.n.0/compose/Workstation/x86_64/os/

as the install source to do a net-installation. When clicking OK after
entering that install source to return to the anaconda hub,
anaconda stops “An unknown error has occured”. When clicking on
“More info...” I can see a Python backtrace.
Comment 1 Mike FABIAN 2013-09-24 13:46:58 UTC 
Created attachment 802252 [details]
an-unknown-error-has-occured-python-backtrace.png
Comment 3 Mike FABIAN 2013-09-24 13:52:49 UTC 
Created attachment 802255 [details]
anaconda-tb-dL1koU
Comment 4 Vratislav Podzimek 2013-09-24 14:07:26 UTC 
This is the same issue as described in bug #1004889
Comment 5 Chris Lumens 2013-09-24 14:10:35 UTC 

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