local provider makes assumptions about libvirtd default network setup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Medium
|
Clint Byrum | ||
Bug Description
If a users local libvirtd network configuration is anything other that the stock:
name: default
bridge: virbr0
The juju local provider fails to work properly.
It would be great if juju could create new, juju environment specific network configurations as an environment is bootstrapped - this would avoid conflicts with any changes to the stock network configuration e.g.:
juju bootstrap -e mylocal
juju creates a network called 'mylocal' using an appropriately named bridge (maybe mylocal) and a DHCP range with does not conflict with anything else already configured on the users local system.
After users not correctly placing their userid in the libvirtd group, this was the second most common issue I saw at charm school during UDS when people try to get started with the local provider.
Related branches
- Kapil Thangavelu (community): Approve
-
Diff: 2440 lines (+724/-859)29 files modifiedMakefile (+1/-1)
juju/agents/tests/test_base.py (+1/-1)
juju/control/options.py (+1/-1)
juju/lib/lxc/__init__.py (+72/-94)
juju/lib/lxc/data/juju-create (+0/-156)
juju/lib/lxc/data/lxc.conf (+0/-3)
juju/lib/lxc/tests/test_lxc.py (+90/-92)
juju/lib/service.py (+19/-7)
juju/lib/tests/test_service.py (+17/-1)
juju/machine/tests/data/test_get_container (+44/-0)
juju/machine/tests/test_unit_deployment.py (+24/-40)
juju/machine/unit.py (+55/-59)
juju/providers/common/cloudinit.py (+79/-7)
juju/providers/common/tests/data/cloud_init_branch (+1/-1)
juju/providers/common/tests/data/cloud_init_branch_trunk (+1/-1)
juju/providers/common/tests/data/cloud_init_no_machine_id (+10/-0)
juju/providers/common/tests/data/cloud_init_ppa_apt_proxy (+39/-0)
juju/providers/common/tests/test_cloudinit.py (+36/-2)
juju/providers/common/utils.py (+7/-1)
juju/providers/ec2/tests/data/launch_cloud_init_branch (+1/-1)
juju/providers/local/__init__.py (+17/-14)
juju/providers/local/agent.py (+3/-9)
juju/providers/local/files.py (+11/-9)
juju/providers/local/network.py (+66/-118)
juju/providers/local/tests/test_agent.py (+13/-4)
juju/providers/local/tests/test_files.py (+9/-51)
juju/providers/local/tests/test_network.py (+106/-184)
juju/providers/local/tests/test_provider.py (+1/-1)
setup.py (+0/-1)
| summary: |
- local provider makes assumptions about libvirtd network setup + local provider makes assumptions about libvirtd default network setup |
| Norberto Bensa (nbensa) wrote | #1 |
| James Page (james-page) wrote | #2 |
| Kapil Thangavelu (hazmat) wrote Re: [Bug 997667] Re: local provider makes assumptions about libvirtd default network setup | #3 |
| Clint Byrum (clint-fewbar) wrote | #4 |
| Changed in juju: | |
| status: | New → In Progress |
| milestone: | none → 0.6 |
| importance: | Undecided → Medium |
| assignee: | nobody → Clint Byrum (clint-fewbar) |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
I got bite by this one yesterday.
In my system, libvirt bridge is called 'vbr-default-0' (I think is the current default as I can't remember renaming it) and so 'juju deploy' doesn't work.