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:
we just found a bug (behaviour - described in 626324) in libvirt which do not use force eject, that results a regression from our side, as in case image was mounted on guest machine, it will fail in the change\eject operation, and would produce an exception in GUI.
This bug should be solved on all layers, meaning, libvirt should expose a way in their API to ask for force eject, which is an RFE, thus, vdsm should produce valid error message to GUI in case it fails.
I assume backend has work here as well, though lets start with vdsm
repro steps: see BZ 626324.
Dan, it looks like behavior is now correct from vdsm perspective; however, I don't get any message from backend\frontend.
do you think we should open a different bug for it ?
Thread-3763::DEBUG::2010-09-27 14:10:29,985::clientIF::39::vds::(wrapper) [10.35.70.2]::call changeCD with ('75741acb-ad1c-4082-b80e-1aea87dbbcb4', '/rhev/data-center/6d511a8e-4cc5-49bc-b39d-28ceac510996/d7b8cd6e-
7e11-425b-b03f-83f5e721ea87/images/11111111-1111-1111-1111-111111111111/Fedora-10-x86_64-DVD.iso') {}
Dummy-147::DEBUG::2010-09-27 14:10:30,137::misc::123::Storage.Misc.excCmd::(execCmd) SUCCESS: <err> = '8000+0 records in\n8000+0 records out\n4096000 bytes (4.1 MB) copied, 4.99035 s, 821 kB/s\n'; <rc> = 0
Thread-3763::DEBUG::2010-09-27 14:10:30,777::clientIF::44::vds::(wrapper) return changeCD with {'status': {'message': 'Failed to change disk image', 'code': 41}}
verified on vdsm 4.9-20 (there is still an issue with rhevm).
vdsm reports the following error:
Thread-4375::DEBUG::2010-10-25 15:46:12,346::clientIF::45::vds::(wrapper) return changeCD with {'status': {'message': 'Failed to change disk image', 'code': 41
}}
repro steps:
1) run guest in run level 5
2) change CD and mount any iso
3) try to change CD