Bug 864961

logs?

Created attachment 624920 [details]
Logs

Relevant data appears at the end of logs.

Why is this a bug?
VM properties did not change, the display type is still VNC. 

Run Once only overrides the current startup configuration which is not listed since it's transient. When you get a VM object you are supposed to get the configuration, so you may properly be able to edit it. 

I think the solution may be and RFE (if not exists) to extend the API to retrieve run once parameters, if the VMs was started using run once.

Oded. per comment #3, please find out if there is another way to get this info, or convert this to an RFE to retrieve the run-once properties of a running VM.

(In reply to comment #4)
> Oded. per comment #3, please find out if there is another way to get this
> info, or convert this to an RFE to retrieve the run-once properties of a
> running VM.

the meaning of the run-once command is: do-not-store, 
if you want to persist vm config, update vm.

also such RFE won't be feasible. as it will break run-once concept.

When I run the VM from UI using run once and choosing X display type , I see it with X display type under VM's tab , even when it defined with Y as default display type.
Shouldn't the behavior be the same in API / CLI ?

(In reply to comment #6)
> When I run the VM from UI using run once and choosing X display type , I see
> it with X display type under VM's tab , even when it defined with Y as
> default display type.
> Shouldn't the behavior be the same in API / CLI ?

if vm running yes, if it's down, no, what was the state of the vm?

(In reply to comment #7)
> (In reply to comment #6)
> > When I run the VM from UI using run once and choosing X display type , I see
> > it with X display type under VM's tab , even when it defined with Y as
> > default display type.
> > Shouldn't the behavior be the same in API / CLI ?
> 
> if vm running yes, if it's down, no, what was the state of the vm?

When defining the VM with default display type=VNC, then running the VM using run-once with display type=spice, we get different values in UI and API (while VM is running):
In UI - display type = spice
In API - display type = VNC

> When defining the VM with default display type=VNC, then running the VM
> using run-once with display type=spice, we get different values in UI and
> API (while VM is running):
> In UI - display type = spice
> In API - display type = VNC
then I suppose GUI should be changed to rather show the permanent value, just so you won't overwrite it accidentally while editing VM when it's run via Run Once.

sounds like a minor bug

(In reply to comment #9)
> > When defining the VM with default display type=VNC, then running the VM
> > using run-once with display type=spice, we get different values in UI and
> > API (while VM is running):
> > In UI - display type = spice
> > In API - display type = VNC
> then I suppose GUI should be changed to rather show the permanent value,
> just so you won't overwrite it accidentally while editing VM when it's run
> via Run Once.
> 
> sounds like a minor bug

It is not minor issue since those details are important and cannot retrieved easily,  they also don't appear in the events logs.

> > sounds like a minor bug
> 
> It is not minor issue since those details are important and cannot retrieved
> easily,  they also don't appear in the events logs.

don't understand.
run time details are in the Vm status tab (the bottom one).
These values should not be presented anywhere else, since it's only "run once" - comment #5.
Or do you have anything else in mind?

Link : http://gerrit.ovirt.org/#/c/8822/

Commit Hash: bab798835a194b4890f406bc30e72ebcf4ee70f3

OK - SF3

Display type now shows the correct value when using 'run once', and default display type is shown after VM powers off, as expected.

3.2 has been released

3.2 has been released