Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Media Lock Test (Logo) job need to stop transactional resouce manager ,but it always failed
Version-Release number of selected component (if applicable):
2.6.32-338.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Start Guest with virtio-scsi cdrom (or passthrough) ,make sure no disks in it
root 19961 19860 9 16:12 pts/2 00:01:42 /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic,family=0xf -usb -device usb-tablet -device virtio-scsi-pci,id=scsi0 -drive file=win2k8-R2-SCSI-49.raw,format=raw,serial=mike,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop -device ide-drive,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -netdev tap,sndbuf=0,id=hostnet0,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet0,mac=00:52:47:11:31:46 -uuid 0ccc9ba0-b793-4252-bd71-a366e3de6f94 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-winR2-scsi,server,nowait -mon chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -drive format=raw,serial=mike_cdrom1,if=none,id=drive-cdrom1,cache=none,media=cdrom,werror=stop,rerror=stop -device scsi-cd,bus=scsi0.0,drive=drive-cdrom1,id=cdrom1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -M rhel6.4.0 -vga cirrus -drive format=raw,cache=none,werror=stop,rerror=stop,id=ide-cdrom00,media=cdrom,if=none -device ide-drive,id=cdrom00,drive=ide-cdrom00
2.in the guest fsutil resource stop D:
Actual results:
It shows "The Disk Structuer is corrupted and unreadable
Expected results:
it should prompts a msg with "There is no disk in the drive,Please intert a disk into driver D:" (referring to the screendump
Additional info:
Comment 3RHEL Program Management
2012-12-28 06:47:27 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
WHQL Log Description:
Filter Number:4107 Row:517 ] - The Media Lock Test (LOGO) (Manual Test) may fail a user who is incorrectly interpreting the manual eject check box.
5 of 44
Issue Resolution
Selecting Mechanical Ejection within the device console storage device submission wizard means that the only way to eject is through mechanical means and not programmatically thorough software. The test will fail if the device can only be ejected manually (not through software) and you do not select Mechanical Ejection which is called 'Manual ejection only' in the device console submission wizard page. For example, If this is a hard disk within an enclosure, and you only support ejecting the hard disk through a button on the enclosure, please select Mechanical Ejection only within the wizard page.