Bug 1015173 - Attempt to cancel ISO verification crashes anaconda
Summary: Attempt to cancel ISO verification crashes anaconda
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: David Shea
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 14:53 UTC by Tomas Capek
Modified: 2014-06-18 01:39 UTC (History)
4 users (show)

Fixed In Version: anaconda-19.31.38-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 12:09:01 UTC
Target Upstream Version:

Attachments (Terms of Use)
anaconda traceback (344.85 KB, text/plain)
2013-10-03 15:43 UTC, Tomas Capek 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tomas Capek 2013-10-03 14:53:10 UTC 
Steps to Reproduce:
1. In the Installation Source spoke, select a valid ISO file
2. Click "Verify"
3. Try to interrupt the verification process by clicking the Cancel button... Oops, there is no Cancel button
4. Hit Ecs a couple of times


Actual results:

anaconda crashes with a traceback


Expected results:

Allow users to interrupt the verification process properly, preferably by providing the Cancel button.
Comment 1 David Shea 2013-10-03 15:06:20 UTC 
What version of anaconda were you running? Can you attach the traceback to this bug?
Comment 3 Tomas Capek 2013-10-03 15:43:39 UTC 
Created attachment 807158 [details]
anaconda traceback

I was on 19.31.17-1 but can confirm that the bug occurs on version 21 as well.
Comment 4 David Shea 2013-12-10 19:17:28 UTC 
Just need to cherry-pick 738e99443f9d5ede940a06cabf6e944da51f5894 to rhel7-branch
Comment 7 Ludek Smid 2014-06-13 12:09:01 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.