It looks like any LXD I deploy to an instance on AWS is now inheriting the constraints from the host, this is causing my LXD to fail across the board.
This is slightly difficult to reproduce, as you must have spaces and subnets defined on AWS. This bug does not show do not add any 'spaces' constraints. The following will succeed: $ juju deploy ubuntu # gets machine id 0 $ juju deploy ubuntu ubuntu-lxd --to lxd:0 The following will cause the lxd deploy to fail: $ juju deploy ubuntu --constraints "spaces=myspace" # gets machine id 0 $ juju deploy ubuntu ubuntu-lxd --to lxd:0 The odd thing about this is, that it didn't start happening until this week. I've been harping on this use case for a while now with no such problems, then Monday morning rolls around, I go to spin up some new lxd envs, and nothing .... I've been blocked all week from sending any deploys. This is a critical issue for me, any help would be greatly appreciated. https://bugs.launchpad.net/juju/+bug/1684143
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
