Bug 578160

Summary:	Differentiate between "no image found" and "no checksum found" when checking media.
Product:	[Fedora] Fedora	Reporter:	Radek Vykydal <rvykydal>
Component:	anaconda	Assignee:	Radek Vykydal <rvykydal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	jonathan, kparal, rvykydal, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-14.3-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	578151
Clones:	586351 586359 (view as bug list)		Environment:
Last Closed:	2010-11-01 11:48:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	586351, 586359

Description Radek Vykydal 2010-03-30 12:59:07 UTC

+++ This bug was initially created as a clone of Bug #578151 +++

Created an attachment (id=403477)
screenshot

Description of problem:
Anaconda Stage 1 offers to test the checksum of install media. When you hit Test and you have no media in your drive, you get this message (see screenshot):

"Error: Unable to read the disc checksum from primary volume descriptor. This probably means the disc was created without adding the checksum."

What's wrong about that:
1. *primary volume descriptor* - that's hacker's language, not end user's language. User has no idea what you are talking about. Please rephrase to more user friendly language.
2. The message should be different when:
a) there is media in the drive but it has no checksum support
b) there is no media in the drive
Currently, the same message is used for both cases, which is wrong.

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

How reproducible:
always

Steps to Reproduce:
1. When anaconda offers you to test media checksum, remove media from drive.
2. Hit Test.

--- Additional comment from rvykydal on 2010-03-30 08:54:26 EDT ---

(In reply to comment #0)
 
> What's wrong about that:
> 1. *primary volume descriptor* - that's hacker's language, not end user's
> language. User has no idea what you are talking about. Please rephrase to more
> user friendly language.

Yes, I'd use "disc image" or "iso image" instead

> 2. The message should be different when:
> a) there is media in the drive but it has no checksum support
> b) there is no media in the drive
> Currently, the same message is used for both cases, which is wrong.

This will be fixed when I push already review-acked changes in isomd5sum and related anaconda changes (which will happen as soon as I get ACLs needed to build Fedora isomd5sum).


I'll keep this bug to track 1. and clone another bug to track 2.

Comment 1 Radek Vykydal 2010-03-30 15:57:47 UTC

(In reply to comment #0)
 
> > 2. The message should be different when:
> > a) there is media in the drive but it has no checksum support
> > b) there is no media in the drive
> > Currently, the same message is used for both cases, which is wrong.
> 
> This will be fixed when I push already review-acked changes in isomd5sum and
> related anaconda changes (which will happen as soon as I get ACLs needed to
> build Fedora isomd5sum).

Should be fixed in version 14.3-1 of anaconda.

Comment 2 Bug Zapper 2010-07-30 11:13:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Kamil Páral 2010-11-01 11:48:40 UTC

I tested with anaconda-14.22 and this is fixed. Closing this bug.