cpu-cores constraint no longer respected

Bug #1755580 reported by Jeff Pihach on 2018-03-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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://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)

WORKS (cores)

Jeff Pihach (hatch) wrote :

The GUI issue is for vsphere but the issue also happens on GCE (possibly others as well)

description: updated
Nicholas Skaggs (nskaggs) wrote :

Can you provide a log confirming this? It seems like this is an API issue with your call, but not an issue on the cli.

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: bitesize
Jeff Pihach (hatch) wrote :

@nskaggs the calls are outlined in the original description.

It's also interesting to note that the machine values returned by the megawatcher use 'cpu-cores' and not the newer 'cores'. So it seems like this change was made but never finalized throughout the codebase with an incremented facade.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers