Bug #1238

undefined SIZE changes the number of arguments of the TM scripts

Added by Jaime Melis about 9 years ago. Updated about 9 years ago.

Status:ClosedStart date:04/17/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:


Category:Core & System
Target version:Release 3.6
Resolution: Pull request:
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.


#1 Updated by jordan pittier about 9 years ago

I somehow already predicted this issue here : http://dev.opennebula.org/issues/179#note-3

'just bragging ;)

#2 Updated by Ruben S. Montero about 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....

#3 Updated by Ruben S. Montero about 9 years ago

  • translation missing: en.field_story_points set to 0

Also available in: Atom PDF