juju picking randomly from available machines instead of best fit

[Evan]

If I have a deployer service config like the following:

services:
  B:
    constraints: mem=8192M
  A:
    constraints: mem=1024M

And then do:

juju add-machine --constraints=mem=8192M
juju add-machine --constraints=mem=1024M

I end up with a 8GB machine 1, and 1GB machine 2. Now, running juju-deployer over the deployment config pushes service A to machine 1 (8GB) and spawns a third instance with 8GB of RAM.

I had expected juju would attempt to place each service on the smallest instance it could find that met the constraints. In this circumstance, I would expect it to use the two machines provided that exactly match the constraints.

Running juju add-machine in the order expected by deployer works around this issue.

juju-core 1.20.1
juju-deployer 0.4.3

[Kapil Thangavelu (hazmat)]

primarily a core bug, marking invalid for deployer.

[Heitor (heitorpbittencourt)]

Is this still happening?

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.