Bug #5529

Sunstone: unable to set CPU first, it always get values from vCPU

Added by kvaps kvaps almost 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:11/02/2017
Priority:HighDue date:
Assignee:Abel Coronado% Done:

100%

Category:Sunstone
Target version:Release 5.4.3
Resolution:fixed Pull request:
Affected Versions:OpenNebula 5.4.2

Description

- Try to create new vm, or resize existing.
- Fill the CPU field (before)
- Fill the vCPU field (after)
- Disfocus vCPU field and look for CPU field - it will be overriden by vCPU value too.
(If you click "Apply" instead disfocusing it will be also applied)

Associated revisions

Revision 2c5e04da
Added by Abel Coronado almost 3 years ago

B #5529: Unable to set CPU first, it always get values from vCPU (#558)

Revision f7dd0e7d
Added by Abel Coronado almost 3 years ago

B #5529: Unable to set CPU first, it always get values from vCPU (#558)

(cherry picked from commit 2c5e04dad53406ef1098fa485f25561c877d5525)

History

#1 Updated by Abel Coronado almost 3 years ago

  • Target version set to Release 5.4.4
  • % Done changed from 0 to 100
  • Resolution set to fixed

#2 Updated by Tino Vázquez almost 3 years ago

  • Target version changed from Release 5.4.4 to Release 5.4.3

#3 Updated by Tino Vázquez almost 3 years ago

  • Status changed from Pending to Closed

Also available in: Atom PDF