Bug 688216 - autoeject flag no longer works
Summary: autoeject flag no longer works
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 15:30 UTC by Diana Chinces
Modified: 2012-05-23 15:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-23 15:33:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Diana Chinces 2011-03-16 15:30:50 UTC
Description of problem:
when the autoeject flag is set, it does not eject the cd on reboot

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


How reproducible:


Steps to Reproduce:
1. start in stage2 environment
2. echo 1 > /proc/sys/dev/cdrom/autoeject
3.
  
Actual results:
The cd is ejected on next reboot.

Expected results:
The cd is not ejected on next reboot.

Additional info:

Comment 5 RHEL Program Management 2011-04-04 02:45:30 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2011-10-07 15:26:38 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 7 Prarit Bhargava 2012-04-30 14:03:08 UTC
Diana, I finally found sometime to return to this old BZ and tried your test.  I can't reproduce this in earlier versions of RHEL or even upstream.

Are you using a RHEL certified system?

Thanks,

P.


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