see also bug #1657850 that we probably shouldn't just be using the 'next
available 10.0.x' address. (This was the original algorithm used by LXD
when we added support, but they have changed their algorithm since
then.)

** Package changed: juju (Ubuntu) => juju

** Changed in: juju
       Status: New => Confirmed

** Changed in: juju
    Milestone: None => 2.1.1

** Also affects: juju/2.1
   Importance: Undecided
       Status: New

** Changed in: juju
    Milestone: 2.1.1 => 2.2.0

** Changed in: juju/2.1
       Status: New => Confirmed

** Changed in: juju/2.1
   Importance: Undecided => High

** Changed in: juju/2.1
    Milestone: None => 2.1.1

** Changed in: juju
     Assignee: juju hackers (juju) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665648

Title:
  Juju 2.0.3 fails to deploy LXD container lxdbr0 overlapping subnets

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to