Bug 754919 - bluray: not choosing the most capable media type as default
Summary: bluray: not choosing the most capable media type as default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 1.4
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact: Guangze Bai
URL:
Whiteboard:
Depends On:
Blocks: 767775 773757
TreeView+ depends on / blocked
 
Reported: 2011-11-18 08:22 UTC by Guangze Bai
Modified: 2015-02-08 21:37 UTC (History)
4 users (show)

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.
Clone Of:
Environment:
Last Closed: 2012-06-05 21:36:25 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0711 0 normal SHIPPED_LIVE v7 bug fix and enhancement update 2012-06-06 01:26:37 UTC

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
Note You need to log in before you can comment on or make changes to this bug.