Bug 1108676

Summary:	Run once vm via REST with <pause>true</pause> parameter, save this parameter true also in next runs
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	acathrow, bazulay, eedri, gklein, iheim, juan.hernandez, lpeer, mavital, michal.skrivanek, obasan, oliel, oramraz, Rhev-m-bugs, sherold, tpoitras, yeylon
Target Milestone:	---	Keywords:	AutomationBlocker, ZStream
Target Release:	3.4.1
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, a "pause" parameter was not functioning properly. The RESTAPI was only passing the parameter to the backend if the value was "true". This meant that any VMs configured to start paused by default could not be started normally via the RESTAPI. Now, a patch has changed the RESTAPI to always pass the value of the "pause" parameter to the backend, regardless of its value. As a result, the pause parameter works properly.	Story Points:	---
Clone Of:	1095635	Environment:
Last Closed:	2014-07-29 16:24:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1095635
Bug Blocks:

Comment 2 Artyom 2014-06-26 06:01:42 UTC

Checked on av10(3.4.1-0.23.el6ev)
Still if I create new vm and start it via run once with pause enabled and with attached floppy, pause flag stay checked after I stop vm.
If after it I remove flag manually and again run once vm(pause, attached floppy) flag removed automatically after vm stopped.

Comment 4 Artyom 2014-07-14 11:10:20 UTC

Verified on rhevm-3.4.1-0.25.el6ev.noarch

Comment 6 errata-xmlrpc 2014-07-29 16:24:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0960.html