+++ This bug was initially created as a clone of Bug #1318212 +++

Description of problem:
When increasing VM memory via rhevm-shell. The default behaviour is to hot-plug the memory. This does not have to be possible due to the compatibility version for instance.

Version-Release number of selected component (if applicable):
rhevm-cli-3.6.2.0-1.el6ev

How reproducible:
100%

Steps to Reproduce:
1. Start a VM on a cluster with 3.5 compatibility version.
2. Try to updte the memory: update vm ${VM_NAME} --memort ${MEMORY_SIZE}

Actual results:
The memory is not updated and engine reports an error in the engine.log

Expected results:
Add possibility to set the memory for next run.

Additional info:
This is a regression as this was possible in RHEV 3.5

A possible way to achieve is via curl:

curl -X PUT -H "Accept: application/xml" -H "Content-Type: application/xml" -u admin@internal:password --cacert /etc/pki/ovirt-engine/ca.pem -T data.xml 'https://rhevm36/ovirt-engine/api/vms/a774093d-fb09-4fb7-aff3-989d7c3755c1;next_run'

--- Additional comment from Juan Hernández on 2016-03-16 07:30:24 EDT ---

There are two reasons why this doesn't work. First is that the "next_run" parameter isn't documented in the metadata of the API, thus from the point of view of the generators of the SDKs it doesn't exist.

The second reason is that currently the Python SDK doesn't support URL parameters in "update" operations. The CLI obtains the description of the API inspecting the Python SDK. Thus, from the point of view of the CLI, the "next_run" parameter won't exist even if it is added to the metadata of the API. To support it the generator of the SDK will need to be improved to support URL parameters (similar to bug 1311495), then the SDK will need to be regenerated.

I'm moving the bug to the ovirt-engine component, so that we can add "next_run" to the documentation. Then I will clone this bug for the Python SDK.