Bug #4355

CURRENT_VMS does not accept string values

Added by OpenNebula Systems Support Team about 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:02/22/2016
Priority:NormalDue date:
Assignee:-% Done:


Category:Core & System
Target version:Release 5.0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14


CURRENT_VMS = "1" is not valid, while CURRENT_VMS = 1 is valid. On the other hand, both CLUSTER_ID="100" and CLUSTER_ID=100 are valid.

Associated revisions

Revision 1add1cfb
Added by Ruben S. Montero about 5 years ago

bug #4355: CURRENT_VMS can be now of any type. Better handling of
ObjectXML::search templates


#1 Updated by Ruben S. Montero about 5 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF