cpu-cores constraint no longer respected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Juju version: 2.3.4-xenial-amd64
When making a request over the API for a 4 core CPU if the call uses the legacy key 'cpu-cores' it will disregard that constraint when requesting a new machine. If you send the request using the 'cores' constraint then it will create a machine with the appropriate number of cores.
This has caused a regression in the GUI: https:/
DOESN'T WORK (cpu-cores)
{"type"
WORKS (cores)
{"type"
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bitesize |
The GUI issue is for vsphere but the issue also happens on GCE (possibly others as well)