cmd/juju: local provider doesn't give a clear explanation when lxc is not configured correctly
Bug #1216775 reported by
Dave Cheney
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Medium
|
Tim Penhey | ||
Bug Description
Reported via #juju irc channel.
local provider doesn't give a clear explanation of what is wrong when the lxc bridge mode interface is missing.
sprugonimda@hq:~$ sudo juju -v bootstrap
2013-08-26 06:30:39 INFO juju.environs.local environprovider
2013-08-26 06:30:39 ERROR juju.environs.local net.go:18 cannot find network interface "lxcbr0": net: no such interface
2013-08-26 06:30:39 ERROR juju.environs.local environprovider
2013-08-26 06:30:39 ERROR juju supercommand.go:235 command failed: net: no such interface
error: net: no such interface
Related branches
lp:~thumper/juju-core/configurable-lxc-bridge
- Juju Engineering: Pending requested
-
Diff: 236 lines (+68/-40)5 files modifiedprovider/local/config.go (+6/-0)
provider/local/config_test.go (+39/-28)
provider/local/environ.go (+15/-11)
provider/local/environprovider.go (+7/-0)
provider/local/instance.go (+1/-1)
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| milestone: | 1.13.3 → 1.15.0 |
| Changed in juju-core: | |
| milestone: | 1.15.0 → 1.16.0 |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Tim Penhey (thumper) |
| assignee: | Tim Penhey (thumper) → nobody |
| Changed in juju-core: | |
| assignee: | nobody → Tim Penhey (thumper) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 1.16.0 → 1.15.1 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
To expand slightly: the person who reported this had LXC installed, but they had modified their configuration to use br0 instead of lxcbr0. This is why the pre-requisite checker is not complaining (it just checks LXC userspace tools are available) .