Bug 1002487

Summary: bug occurs when I change the installation source
Product: [Fedora] Fedora Reporter: lnie <lnie>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, lnie, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
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-04 13:01:56 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
packaging.log
none
syslog
none
program.log
none
anaconda.log
none
step1.png
none
step2.png
none
step4.png
none
step3.png
none
anaconda-tb-V3D2UN none

Description lnie 2013-08-29 10:10:20 UTC 
Description of problem:

 Do a default install,change the installation source twice,bug occurs.Actually,
 I thought maybe this version of anaconda is too brittle(as it's alpha Tc2) ,so I click into and out"INstallation destination",but unfortunately or fortunately,no bug occurs.

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

F20-Alpha-Tc2 (DVD)
How reproducible:

always
Steps to Reproduce:
1.Do a default install
2.change the install source to "http://download.fedoraproject.org/...",click"Done"
3.after the error checking ,change install source again,and click"Done",bug occurs

Actual results:
 bug occurs

Expected results:
 no bug occurs,even change "installation source" many times.

Additional info:
Comment 1 lnie 2013-08-29 10:11:00 UTC 
Created attachment 791677 [details]
packaging.log
Comment 2 lnie 2013-08-29 10:11:40 UTC 
Created attachment 791678 [details]
syslog
Comment 3 lnie 2013-08-29 10:12:12 UTC 
Created attachment 791679 [details]
program.log
Comment 4 lnie 2013-08-29 10:12:51 UTC 
Created attachment 791680 [details]
anaconda.log
Comment 5 David Shea 2013-08-29 13:55:41 UTC 
Can you be more specific? What bug occurs? Is there a traceback? Can you attach the traceback data to this bug?
Comment 6 lnie 2013-08-30 05:13:40 UTC 
As,you can see in the attachment,anaconda crashed.I thought the logs and my specific description would be enough，sorry for the time. To help you figure out the problem,I attach the step-by step sreen shots here.
Comment 7 lnie 2013-08-30 05:15:56 UTC 
Created attachment 792018 [details]
step1.png
Comment 8 lnie 2013-08-30 05:17:00 UTC 
Created attachment 792019 [details]
step2.png
Comment 9 lnie 2013-08-30 05:18:18 UTC 
Created attachment 792020 [details]
step4.png
Comment 10 lnie 2013-08-30 05:18:56 UTC 
Created attachment 792021 [details]
step3.png
Comment 11 David Shea 2013-09-03 20:17:30 UTC 
Created attachment 793348 [details]
anaconda-tb-V3D2UN
Comment 12 David Shea 2013-09-03 20:24:26 UTC 
lnie, the log files you attached do not contain information about the crash. When anaconda crashes, the crash data is written to a file named /tmp/anaconda-tb-*. I've attached the traceback from a crash that I was able to create. Is this the same bug you are seeing? You can also see the crash data by clicking on the "More Info" link in the window you see in Step 4. If this is the same crash, you should see the message, "AttributeError: 'FC3_Cdrom' object has no attribute 'noverifyssl'". If not, please attach the anaconda-tb file in /tmp.
Comment 13 David Shea 2013-09-03 20:50:54 UTC 
If this crash is the same as the one I encountered, it is fixed by the fix for bug 1001081.
Comment 14 lnie 2013-09-04 03:21:11 UTC 
David,they are the same.I cann't believe that I forgot to attach that important one!I should sent myself to face the wall right now,so see you in next bug,haha.
Comment 15 David Shea 2013-09-04 13:01:56 UTC 
No problem, glad we could get it worked out