Bug 1026306 - Tools iso gets mounted to untooled VM even when CD is unchecked in "Run Once" dialog
Summary: Tools iso gets mounted to untooled VM even when CD is unchecked in "Run Once"...
Keywords:
Status: CLOSED DUPLICATE of bug 1054743
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.5.0
Assignee: Martin Betak
QA Contact:
URL:
Whiteboard: virt
Depends On: 1054743
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 11:40 UTC by David Jaša
Modified: 2014-03-26 13:04 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-26 13:04:17 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25957 0 None None None Never

Description David Jaša 2013-11-04 11:40:48 UTC
Description of problem:
Auto-attaching latest tools iso for untooled Windows VMs is a nice thing to do when doing a generic "start VM" action but it's quite misleading when it kicks in as a result of "Run Once" action with CD to attach leaved as unchecked - the VM configuration should literally match what is entered in "Run Once" dialog (and the tools CD should be enabled by default there)

Version-Release number of selected component (if applicable):
is20.2 / rhevm-backend-3.3.0-0.30.beta1.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. have a Windows VM
2. go to Run Once dialog, expand Boot Options
3. check if "Attach CD" is checked or not
4. uncheck "Attache CD" if checked, hit OK
5. check if VM has CD attached (vdsm.log, libvirt xml, qemu cli, ...)

Actual results:
3. "Attach CD" is unchecked
5. CD is actually attached

Expected results:
3. "Attach CD" should be checked and latest tools (the ones that get attached automagically) should be checked
5. VM should start without CD attached

Additional info:

Comment 1 Michal Skrivanek 2013-11-12 13:14:42 UTC
we probably shouldn't do that when explicitly removed cdrom

Comment 2 Michal Skrivanek 2014-03-26 13:03:28 UTC
depends on refactoring done in bug 1054743 which is too risky to backport this late in 3.4 cycle. postponing and moving to MODIFIED for 3.5

Comment 3 Michal Skrivanek 2014-03-26 13:04:17 UTC

*** This bug has been marked as a duplicate of bug 1054743 ***


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