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

Description of problem:

Trying to (cold or not) move a disk from the CLI, relying on the TAB-TAB or by reading the docs, proves that this operation is not completely supported :

----
# action disk myDisk move --storagedomain-name mySD
get() got an unexpected keyword argument 'name'
----

Juan Hernández gives this workaround :
You can however use the same operation in the context of the VM :
# action disk c6aab66a-b551-4cc5-8628-efe9622c0dce move --vm-identifier myvm --storage_domain-name mysd

and I confirm this is working.

The included doc is wrong, and so is the auto-completion.

Version-Release number of selected component (if applicable):
>> [oVirt shell (connected)]# info
>>
>> backend version: 3.4
>> sdk version    : 3.4.4
>> cli version    : 3.4.0.5
>> python version : 2.6.6.final.0

How reproducible:
Always

Steps to Reproduce:
1. Run an ovirt-shell
2. Try to move a disk following the command above
3. Cry

Actual results:
The disk is just staying there, calm.

Expected results:
The disk is moving towards the wanted storage domain.

Additional info:
See this thread :
http://lists.ovirt.org/pipermail/users/2014-November/029623.html

--- Additional comment from Juan Hernández on 2014-12-01 08:43:27 EST ---

The RSDL metadata should be fixed, then the SDKs need to be regenerated.