| 2018-03-13 20:07:51 |
Jeff Pihach |
description |
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://github.com/juju/juju-gui/issues/3560 as we must support multiple versions of Juju and there doesn't appear to have been a facade bump for this change.
DOESN'T WORK (cpu-cores)
{"type":"Client","request":"AddMachines","params":{"params":[{"jobs":["JobHostUnits"],"series":null,"parent-id":null,"container-type":null,"constraints":{"cpu-cores":4}}]},"version":1,"request-id":17}
WORKS (cores)
{"type":"Client","request":"AddMachines","params":{"params":[{"jobs":["JobHostUnits"],"series":null,"parent-id":null,"container-type":null,"constraints":{"cores":4}}]},"version":1,"request-id":7} |
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://github.com/juju/juju-gui/issues/3560 as we must support multiple versions of Juju and there doesn't appear to have been a facade bump for this change.
DOESN'T WORK (cpu-cores)
{"type":"Client","request":"AddMachines","params":{"params":[{"jobs":["JobHostUnits"],"series":null,"parent-id":null,"container-type":null,"constraints":{"cpu-cores":4}}]},"version":1,"request-id":17}
WORKS (cores)
{"type":"Client","request":"AddMachines","params":{"params":[{"jobs":["JobHostUnits"],"series":null,"parent-id":null,"container-type":null,"constraints":{"cores":4}}]},"version":1,"request-id":7} |
|
