undefined SIZE changes the number of arguments of the TM scripts
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 3.6|
|Affected Versions:||OpenNebula 3.4|
when cloning or linking a disk, the number or argument varies depending if SIZE is set or not in the DISK =  section of the VM.
When SIZE is set:
/path/to/clone src_host:src_source dst_host:dst_path size vm_id datastore_id
When SIZE is not set:
/path/to/clone src_host:src_source dst_host:dst_path vm_id datastore_id
This means that for instance, when size is not set, the VM_ID would be $3, whereas when SIZE is set, it would be $4.
A proposed solution is to set the SIZE to be the character - when SIZE is not set, thus the number of arguments won't change.
#2 Updated by Ruben S. Montero almost 9 years ago
- Status changed from New to Closed
- Assignee changed from Carlos Martín to Ruben S. Montero
Fixed. Now the size is not passed to the drivers, as non of the default drivers needed it. The protocol has been exteneded to include a reference to the VM and Datastore to get further details as the SIZE. Closing this....