Juju does not use constraints when deploying to a container

[Johan Ehnberg]

Running Juju 1.20.12-trusty-amd64 on MaaS.

May be related to:
https://code.launchpad.net/~thumper/juju-core/kvm-constraints/+merge/197815

Setting constraints does not affect the creation of KVM containers.

johan@maas:~$ juju deploy --to kvm:2 --constraints "mem=2G cpu-cores=2" ubuntu test-ubuntu
Added charm "cs:trusty/ubuntu-0" to the environment.

johan@maas:~$ juju status test-ubuntu
environment: maas
machines:
  "2":
    agent-state: started
    agent-version: 1.20.12
    dns-name: ajbwc.maas.molnix.com
    instance-id: /MAAS/api/1.0/nodes/node-2aadeb06-6a86-11e4-8be8-0021702cb7de/
    series: trusty
    containers:
      2/kvm/4:
        agent-state: pending
        instance-id: juju-machine-2-kvm-4
        series: trusty
        hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M
    hardware: arch=amd64 cpu-cores=2 mem=6144M
services:
  test-ubuntu:
    charm: cs:trusty/ubuntu-0
    exposed: false
    units:
      test-ubuntu/0:
        agent-state: pending
        machine: 2/kvm/4

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robie Basak (racb)]

Sending this upstream in the first instance, as it is unlikely to be an Ubuntu packaging issue.

[Dimiter Naydenov (dimitern)]

Confirmed this happens with both KVM and LXC containers - when --to is given along with --constraints specifying placement the latter is ignored.

[Michael Iatrou (michael.iatrou)]

juju 2.0-beta6-trusty-amd64 is affected by it too.

[Martin Packman (gz)]

From bug 1399613 this also affects add-machine with container syntax.

[Ante Karamatić (ivoks)]

Dear juju team, I believe this has been fixed for some time. See bug 1626597.