Comment 10 for bug 1685782

Do you have a constraint or binding on the application you are trying to
deploy as well? Or is it only provisioning the machine that has a space
constraint?

I wonder if you're actually running into this one:
logger.Debugf("container %q not qualified to a space, host machine %q is
using spaces %s",
containerId, m.Id(), network.QuoteSpaceSet(hostSpaces))

Can you enable DEBUG level logging and include the log output from the
controller when trying to deploy the container?

  juju model-config -m controller
logging-config="<root>=INFO;juju.network=DEBUG"

is probably sufficient. (the actual module where that would be logged looks
to be juju.network.containerizer)
I often just do:
    juju model-config -m controller logging-config="<root>=DEBUG"
when I'm not sure.

It *might* also be useful to do:
  juju model-config -m controller
logging-config="<root>=DEBUG;juju.state=TRACE"
but that is likely to be a *lot* of logging.

I'm a bit curious what this would be reporting:
logger.Tracef("machine %q found constraints %s and bindings %s",
m.Id(), network.QuoteSpaceSet(spaces), network.QuoteSpaceSet(bindings))

Which would indicate what spaces we think the container wants to be in,
before we do a final pass.

John
=:->

On Mon, Apr 24, 2017 at 6:51 PM, james beedy <email address hidden> wrote:

> The latest command, `juju
> deploy --to lxd:X --constraints spaces=` does give a new message though
> http://paste.ubuntu.com/24448266/
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1685782
>
> Title:
> juju deployed LXD inherit constraints from the host causing lxd
> deploys to fail
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1685782/+subscriptions
>