Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1116550 - No parameter under vm in REST for "Start in pause mode" flag
No parameter under vm in REST for "Start in pause mode" flag
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.4.0
x86_64 Linux
unspecified Severity high
: ovirt-3.6.0-rc
: 3.6.0
Assigned To: Martin Betak
Artyom
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-06 02:11 EDT by Artyom
Modified: 2016-04-19 21:29 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
The 'Start in Pause Mode' functionality of the Administration Portal has been added to the REST API. Users can now use the '<start_paused>true|false</start_paused>' value when configuring virtual machines.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-04-19 21:29:15 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 30104 master MERGED restapi: Expose Vm#runInPaused property Never

  None (edit)
Description Artyom 2014-07-06 02:11:09 EDT
Description of problem:
No parameter under vm in REST for "Start in pause mode" flag

Version-Release number of selected component (if applicable):
av10

How reproducible:
Always

Steps to Reproduce:
1. Create new vm
2. Check parameter start_in_pause under vm via REST
3.

Actual results:
No parameter

Expected results:
Parameter exist, like for example stateless(<stateless>false</stateless>)

Additional info:
Comment 1 Artyom 2015-04-21 07:28:32 EDT
Verified on ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch
Parameter exist and also update of parameter via REST works fine

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