Bug 754919

Summary:	bluray: not choosing the most capable media type as default
Product:	[Retired] Red Hat Hardware Certification Program	Reporter:	Guangze Bai <gbai>
Component:	Test Suite (tests)	Assignee:	Greg Nichols <gnichols>
Status:	CLOSED ERRATA	QA Contact:	Guangze Bai <gbai>
Severity:	medium	Docs Contact:
Priority:	high
Version:	1.4	CC:	czhang, mqi, rlandry, yshao
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	A bug fix has been added to v7 1.5 that bluray test now will choose the most capable media type to test.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-05 21:36:25 UTC	Type:	---
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:
Bug Blocks:	767775, 773757

Description Guangze Bai 2011-11-18 08:22:59 UTC

Description of problem:

The given bluray drive is most capable of bd-re media type, but the test now choose bd as default

# v7 run -t bluray
...
Would you like to test bd media? (y|n) n
response: n
Please choose the media to be tested:  (bd|bd-r|bd-re) 

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:
The most capable media type (here bd-re) is the default

Additional info:

Comment 8 Caspar Zhang 2012-06-04 07:30:07 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
A bug fix has been added to v7 1.5 that bluray test now will choose the most capable media type to test.

Comment 10 errata-xmlrpc 2012-06-05 21:36:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0711.html