juju doesn't configure lxdbr0 properly with new LXD (>2.3)

Bug #1668547 reported by John A Meinel on 2017-02-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Joseph Phillips
2.3
High
Joseph Phillips

Bug Description

If you bootstrap to xenial, and then upgrade lxd from xenial backports (currently 2.8-0).
When LXD is installed, it creates an LXDBR0 bridge and puts it in the default profile.
However, *it* does not configure that bridge to have IPv4 addresses (ipv4.address: none instead of ipv4.address: auto).

That means that containers come up, and they have an /e/n/i that says they should use DHCP, but the bridge is not configured correctly.

If we are thinking to fix bug #1665648, we should probably fix this as well.
It will come to bite us for anyone using backported LXD on Xenial (which Juju should probably be doing by default), and for newer versions (I think yakkety+ uses newer LXD).

Ian Booth (wallyworld) on 2017-03-01
no longer affects: juju/2.1
Curtis Hovey (sinzui) on 2017-03-24
Changed in juju:
milestone: 2.2-beta1 → 2.2-beta2
Changed in juju:
milestone: 2.2-beta2 → 2.2-beta3
John A Meinel (jameinel) wrote :
Changed in juju:
milestone: 2.2-beta3 → 2.2-beta4
Changed in juju:
milestone: 2.2-beta4 → 2.2-rc1
Tim Penhey (thumper) on 2017-06-01
Changed in juju:
milestone: 2.2-rc1 → none
John A Meinel (jameinel) on 2018-05-14
Changed in juju:
assignee: John A Meinel (jameinel) → nobody
Changed in juju:
assignee: nobody → Joseph Phillips (manadart)
milestone: none → 2.4-rc1
no longer affects: juju/3.0
Changed in juju:
status: Triaged → In Progress
Changed in juju:
status: In Progress → Fix Committed
Joseph Phillips (manadart) wrote :

I uninstalled my LXD snap and reinstalled the deb from xenial, then bootstrapped.

Then I uninstalled LXD and reinstalled from xenial-backports. I got 2.21.

> apt list lxd -a
Listing... Done
lxd/xenial-backports,now 2.21-0ubuntu3~16.04.2 amd64 [installed]
lxd/xenial-updates 2.0.11-0ubuntu1~16.04.4 amd64
lxd/xenial-security 2.0.2-0ubuntu1~16.04.1 amd64
lxd/xenial 2.0.0-0ubuntu4 amd64

The only issue I had was that /var/lib/lxd had ownership of root:root, so I had to set the group back to "lxd" to connect via the socket.

After this, my existing deployment was OK, as was a new bootstrap.

Joseph Phillips (manadart) wrote :

This issue remains if the following sequence is followed:

- Bootstrap.
- Add a machine.
- SSH onto the new machine and install LXD from backports.
- Deploy to, or create a new container on the machine.

This should be rectified by ensuring IPv4 config when interrogating the default bridge.

Changed in juju:
status: Fix Committed → In Progress

Thanks for going through the extra steps to track down the issue.

John
=:->

On Thu, May 17, 2018, 20:11 Joseph Phillips <email address hidden>
wrote:

> This issue remains if the following sequence is followed:
>
> - Bootstrap.
> - Add a machine.
> - SSH onto the new machine and install LXD from backports.
> - Deploy to, or create a new container on the machine.
>
> This should be rectified by ensuring IPv4 config when interrogating the
> default bridge.
>
> ** Changed in: juju
> Status: Fix Committed => In Progress
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1668547
>
> Title:
> juju doesn't configure lxdbr0 properly with new LXD (>2.3)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1668547/+subscriptions
>

Joseph Phillips (manadart) wrote :

I had erroneously thought this fixed in a prior commit.

Based on my testing it is resolved by:
https://github.com/juju/juju/pull/8730

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers