Bug 692414 - Installation continues after failed media check
Summary: Installation continues after failed media check
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: Unspecified
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: 2011-03-31 10:00 UTC by Kamil Páral
Modified: 2011-03-31 12:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-31 12:41:34 UTC
Type: ---


Attachments (Terms of Use)

Description Kamil Páral 2011-03-31 10:00:06 UTC
Description of problem:
In bug #692135 the anaconda media check failed for me. However, after clicking on OK the installation started as usual. See attachment #488766 [details]. I think that's not a good approach. If we know the installation image is corrupted, we shouldn't continue with installation.

Rationale: The user may not notice the error message, very often one only quickly looks over the message and hits OK. Then he can end up with corrupted install/crashing install/etc.

Proposal: When media check fails, show the dialog and offer only "Reboot" button. In the dialog recommend checking the hashsum of the ISO image and burning again.

If the user decides to circumvent the error and install anyway, he can always reboot and skip the media check. But making that harder is better than allowing some people to do that without properly noticing.

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

Comment 1 Chris Lumens 2011-03-31 12:41:34 UTC
Media check is only a best effort - it will never be able to 100% detect error conditions.  Forcing the user to go through a reboot step is more of an annoyance than anything else.  Maybe if media check were perfect, I'd be okay with it.  But it's not and it's never going to be.


Note You need to log in before you can comment on or make changes to this bug.