local provider LXC network bridge name not configurable

Bug #1230306 reported by Eric Williams
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-core
Won't Fix
Low
Unassigned

Bug Description

Environment:

ubuntu precise 12.04
juju-core 1.14.1 (ppa:juju-core/stable)
local provider

environments.yaml:
----
default: local

environments:
    local:
        type: local
        admin-secret: ceb8d811a6e225e8d1608f403dc8cbe1
        # Override the directory that is used for the storage files and database.
        # The default location is $JUJU_HOME.
        # $JUJU_HOME defaults to ~/.juju
        # root-dir: ~/.juju/local
        # Override the storage port if you have multiple local providers, or if the
        # default port is used by another program.
        # storage-port: 8040
        # Override the shared storage port if you have multiple local providers,
        # or if the default port is used by another program.
        # shared-storage-port: 8041

---

- juju bootstrap fails with the following error LXC bridge is not named "lxcbr0"

eric@macmini:~$ sudo juju -v bootstrap
2013-09-25 14:19:46 INFO juju.provider.local environprovider.go:32 opening environment "local"
2013-09-25 14:19:46 ERROR juju.utils network.go:37 cannot find network interface "lxcbr0": net: no such interface
2013-09-25 14:19:46 ERROR juju.provider.local environprovider.go:48 failure setting config: net: no such interface
2013-09-25 14:19:46 ERROR juju supercommand.go:282 command failed: net: no such interface
error: net: no such interface

- LXC containers can be created normally, but juju fails with "net: no such interface"

Being able to specify the LXC bridge name in the environment file would allow juju to function in non-default LXC network configurations.

Use case for this is for connecting Juju-orchestrated services to network bridges that aren't named 'lxcbr0'.

Steps to reproduce:

1. edit /etc/default/lxc and /etc/lxc/lxc.conf to point LXC instances at virbr0 (or any other existing bridge)
2. test with 'lxc-create -n virbr-test -t ubuntu -- -r precise
3. create environments.yaml:

default: local

environments:
    local:
        type: local
        admin-secret: ceb8d811a6e225e8d1608f403dc8cbe1

4. sudo juju -v bootstrap

Expected results:
juju uses default lxc configuration for network bridge name (or is configurable in environments.yaml)

Actual results:
juju fails with error "lxcbr0: net: no such interface"

Thanks,
Eric

Marco Ceppi (marcoceppi)
Changed in juju-core:
status: New → Confirmed
Revision history for this message
John A Meinel (jameinel) wrote :

I think this would let you set up your own br0 and bridge the local containers onto the general network, which could be pretty useful.

Changed in juju-core:
importance: Undecided → Low
status: Confirmed → Triaged
Curtis Hovey (sinzui)
tags: added: addressability local-provider
tags: added: network
Curtis Hovey (sinzui)
Changed in juju-core:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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