Bug 144778 – CDROM test should not leave the media mounted after running

Bug 144778 - CDROM test should not leave the media mounted after running

Summary:	CDROM test should not leave the media mounted after running

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Ready Certification Tests
Classification:	Retired
Component:	cdrom (Show other bugs)
Sub Component:
Version:	2
Hardware:	ia64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Rob Landry
QA Contact:	Rob Landry
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-01-11 09:50 EST by Glen A. Foster
Modified:	2007-04-18 13:18 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-04-29 11:30:12 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Glen A. Foster 2005-01-11 09:50:31 EST

Description of problem: Perhaps it's just personal opinion, or perhaps
there's a regression between the RHEL3 and RHEL4 versions of the CDROM
tests in the certification suites... but when I get the CDROM test to
work (see latest discussions in bug 143219), the media is still
mounted at the end of the test, even though the test passes.

The RHEL3 version does not do this; one can eject the media
immediately following completion of the test.

Version-Release number of selected component (if applicable):
# rpm -qa rhr2-rhel4
rhr2-rhel4-0.9-16.rc1a

Comment 1 Rob Landry 2005-01-11 15:04:26 EST

probably not a bad request; though I don't think it'll get a stop ship
label ATM though.

Comment 2 Rob Landry 2005-04-14 13:53:32 EDT

-17beta should resolve this (actually I believe it's in, though I don't recall when)

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