Bug 136457

Summary: Test fails on CDR-W where log don't show any error or fail
Product: [Retired] Red Hat Ready Certification Tests Reporter: Nabil Azouz <nabil.azouz>
Component: cdromAssignee: Rob Landry <rlandry>
Status: CLOSED CURRENTRELEASE QA Contact: Rob Landry <rlandry>
Severity: low Docs Contact:
Priority: medium    
Version: 2CC: hcp-admin
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-29 15:26:22 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:
Attachments:
Description Flags
CDROM test error log
none
CDROM test output log none

Description Nabil Azouz 2004-10-20 08:03:58 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET 
CLR 1.1.4322)

Description of problem:
Test failed but no error loged

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

How reproducible:
Always

Steps to Reproduce:
1.I modified the hardware.conf file to show as CDROM sdc0(cdr-w,eject)
and I copied the ia64-disc1.iso to /tmp. Test seems to access the CDR-
W and burn data. later ejects and prompts to close and it seems it's 
reading and results shows error. No error shown in error.log nor in 
output.log

Additional info:
Comment 1 Nabil Azouz 2004-10-20 08:10:06 UTC 
Created attachment 105497 [details]
CDROM test error log
Comment 2 Nabil Azouz 2004-10-20 08:10:48 UTC 
Created attachment 105498 [details]
CDROM test output log
Comment 3 Rob Landry 2004-11-11 02:45:34 UTC 
This really happens because cdrom is the default; if the mode
specified in ()'s doesn't exist it will fall back to cdrom.  I'll need
to decide if that's ok behaviour.  Perhaps it would be better to warn
that it didn't recognise it, not certain yet, though most likely.
Comment 4 Rob Landry 2005-04-14 17:01:36 UTC 
Should be addressed in rhr2-1.0-17beta (probably before)