ERROR cannot find network interface "lxcbr0": route ip+net: no such network interface

Bug #1566589 reported by Casey Marshall
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Critical
Unassigned

Bug Description

Now when you install LXD, you have to configure the bridge, like this:

ubuntu@demo:~$ sudo dpkg-reconfigure lxd

I followed the prompts to create lxdbr0, which provides a 10.0.4.1/24 network with NAT:

lxd stop/waiting
lxd start/running, process 2532

However, I can't bootstrap:

ubuntu@demo:~$ juju bootstrap demo lxd --upload-tools
ERROR cannot find network interface "lxcbr0": route ip+net: no such network interface
ERROR invalid config: route ip+net: no such network interface
ubuntu@demo:~$

Turns out that the LXD bridge is hard-coded to lxcbr0. If I dpkg-reconfigure lxd again and name the bridge "lxcbr0", I can bootstrap.

This is definitely going to trip users up. A quick fix would be to change the name of the bridge that Juju expects to the new default "lxdbr0".

However, the user can type anything in that dpkg dialog. Maybe we can get this information out of LXD somehow? Or, allow the user to specify an alternate bridge name when bootstrapping a LXD controller?

Revision history for this message
Casey Marshall (cmars) wrote :

^ LXD bridge is hard-coded to lxcbr0 in Juju, as far as I know.

Maybe there's already a solution to this that I don't know of?

Revision history for this message
Cheryl Jennings (cherylj) wrote :

The newest lxd removed lxcbr0. Tycho has a PR up to fix for the next 2.0 release: https://github.com/juju/juju/pull/5004

Changed in juju-core:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Tycho Andersen (tycho-s)
milestone: none → 2.0-beta4
Revision history for this message
Casey Marshall (cmars) wrote :

Looks like http://reviews.vapour.ws/r/4446/ helps alleviate this issue.

Tycho Andersen (tycho-s)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
Revision history for this message
Slash (slash-u) wrote :

I created my own bridge for lxd, configured it right with it with "lxd init", but juju still does ask for a bridge named lxdbr0:

ERROR cannot find network interface "lxdbr0": route ip+net: no such network interface

My bridge is named differently, is there any way that juju could use a different bridge? or several bridge using different network?

Revision history for this message
Jeff Pihach (hatch) wrote :

Using Juju 2 beta 12 on 16.04.1

It appears that this issue has regressed. When bootstrapping using lxd it expects to find an interface named lxdbr0 even if you use the lxd init, specify something other than lxdbr0, and then go and change the default lxd profile it still outputs the following error message:

root@juju:~# juju bootstrap lxd lxd
ERROR cannot find network interface "lxdbr0": route ip+net: no such network interface
ERROR invalid config: route ip+net: no such network interface

Changed in juju-core:
status: Fix Released → Confirmed
Changed in juju-core:
milestone: 2.0-beta4 → 2.0-beta15
status: Confirmed → Triaged
assignee: Tycho Andersen (tycho-s) → Richard Harding (rharding)
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

In beta12 maybe, but in beta14 JUju got smarte by fixing bug 1575676 (with https://github.com/juju/juju/pull/5871). Now we detect the bridge name set on the default LXD profile and use that. I've just verified it does not occur on master tip (rev 4627592):

$ sudo dpkg-reconfigure -p medium lxd # change only the bridge name from lxdbr0 to e.g. lxdbr1
$ juju bootstrap lxd lxd --upload-tools # success!
$ juju kill-controller lxd -y

$ sudo dpkg-reconfigure -p medium lxd # change back to lxdbr0 for the bride
$ juju bootstrap lxd lxd --upload-tools # success!
$ juju kill-controller lxd -y

Similar steps are part of the linked PR above fixing the mentioned bug.

Changed in juju-core:
status: Triaged → Fix Released
assignee: Richard Harding (rharding) → nobody
milestone: 2.0-beta15 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.