Comment 4 for bug 1819171

My first guess would be that we don't notice that manually provisioned
machines are in valid spaces. Because they are manually provisioned, there
is no Provisioner information about what that subnet actually means. Likely
we could try a best-effort matching "if it looks like 192.168./16 then just
assume it is the same one as the others claim to be".

I could be wrong about it.

John
=:->

On Fri, Mar 8, 2019 at 8:25 PM Peter Sabaini <email address hidden>
wrote:

> PS.: for clarification, the ext-net on machine #0 has both ipv4 and
> ipv6; the interface of the metal actually only has an ipv4 addr bound
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1819171
>
> Title:
> Container on sshprovided machine doesn't respect net binding
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1819171/+subscriptions
>