Bug #4009

Importing vms from EC2 provides a wrong CPU value

Added by Daniel Molina almost 5 years ago. Updated almost 5 years ago.

Status:ClosedStart date:09/29/2015
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Drivers - VM
Target version:Release 4.14.2
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.14

Description

The value is provided as CPU x 100 and the core expects it as CPU only.

Check if this also applies to Azure and Softlayer

Associated revisions

Revision c80e6a27
Added by Jaime Melis almost 5 years ago

Bug #4009: Importing vms from EC2 provides a wrong CPU value

Revision fd1a050e
Added by Jaime Melis almost 5 years ago

Bug #4009: Importing vms from EC2 provides a wrong CPU value

(cherry picked from commit 8023e2146e426b7ca373c74ac632c25988524aad)

History

#1 Updated by Jaime Melis almost 5 years ago

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

Also available in: Atom PDF