Inherited Constraints Causing LXD to Fail

[Drew Freiberger]

On Fri, Apr 21, 2017 at 02:30:39PM -0700, James Beedy wrote:
>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

Would --bindings "myspace" potentially help with this?  Are you trying
to constrain to a machine based on space, or are you trying to link your
interface to a space?  If it's interface linkage, I'd think that using
bindings may be more ppropriate.  Reading the bug, I'm sure there's
still other issues with the process, but I'm wondering if --bindings
might help as a workaround in the interrim.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju/attachments/20170424/812c5e4d/attachment.pgp>