Bug #5008

VM Costs- Memory

Added by maz parmar about 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:02/04/2017
Priority:HighDue date:
Assignee:Juan Jose Montiel Cano% Done:


Target version:Release 5.4
Resolution: Pull request:
Affected Versions:OpenNebula 5.2


using vonecloud 2.2.
There seems to be bug with regards to calculation of VM cost when selection for memory is set as "GB". In template costs are set for memmory/MB/hr and option is list mode or range i.e. 2,4,8 etc When you try and instantiate and you leave the memory default as "GB" selecting different memory size either does not change cost or if it does it does not make sense such as larger memory costing less. If you change memory selection to "MB" then correct costs and changes are shown.

Also notice that next the create virtual machine it just show "Nan/costs".

This effectively makes the costing aspects unusable for customer deploylment


#1 Updated by Tino Vázquez about 4 years ago

  • Status changed from Pending to New
  • Assignee set to Juan Jose Montiel Cano
  • Target version set to Release 5.4

#2 Updated by Juan Jose Montiel Cano almost 4 years ago

  • Category set to Sunstone

#3 Updated by Ruben S. Montero almost 4 years ago

  • Status changed from New to Closed

Also available in: Atom PDF