container addressability When using openstack as provider lxc containers get a hardcoded ip
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
I am trying to deploy automatically 3 ubuntu servers with 3 lxc containers on each of the nodes:
ubuntu:
branch: lp:charms/trusty/ubuntu
num_units: 3
constraints: mem=2G
rabbitmq-
branch: lp:charms/trusty/rabbitmq-server
num_units: 3
constraints: mem=1G
to: [ "lxc:ubuntu=0", "lxc:ubuntu=1", "lxc:ubuntu=2" ]
See full environment: http://
When deployed, the lxc containers are forced into:
LXC_DHCP_
... instead of being plugged into the network of the deployment.
The problem is that these lxcs are not accessible. I was expecting the behaviour to be exactly like the maas provider.
This happens on OpenStack provider and in our opinion should be working on the same way MAAS provider is working.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 1.25.0 |
| tags: | added: lxc network ubuntu-openstack |
| tags: | added: bug-squad |
| Dimiter Naydenov (dimitern) wrote | #2 |
| Changed in juju-core: | |
| milestone: | 1.25-alpha1 → 1.25-beta1 |
| Changed in juju-core: | |
| milestone: | 1.25-beta1 → 1.26-alpha1 |
| Changed in juju-core: | |
| milestone: | 1.26-alpha1 → 1.26-alpha2 |
| Changed in juju-core: | |
| milestone: | 1.26-alpha2 → 1.26.0 |
| Changed in juju-core: | |
| milestone: | 1.26.0 → 2.0-beta5 |
| tags: | added: sts-needs-review |
| Changed in juju-core: | |
| milestone: | 2.0-beta5 → 2.0-beta4 |
| Changed in juju-core: | |
| milestone: | 2.0-beta4 → 2.1.0 |
| tags: |
added: sts-rfe removed: sts sts-needs-review |
| tags: | added: sts |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
| tags: | added: addressable-containers |
| Changed in juju: | |
| milestone: | 2.1.0 → 2.2.0 |
| summary: |
- When using openstack as provider lxc containers get a hardcoded ip + container addressability When using openstack as provider lxc containers + get a hardcoded ip |
| Changed in juju: | |
| milestone: | 2.2-beta1 → 2.2-beta2 |
| Changed in juju: | |
| milestone: | 2.2-beta2 → 2.2-beta3 |
| Changed in juju: | |
| milestone: | 2.2-beta3 → 2.2-beta4 |
| Changed in juju: | |
| milestone: | 2.2-beta4 → 2.2-rc1 |
| Tim Penhey (thumper) wrote | #3 |
| Changed in juju: | |
| milestone: | 2.2-rc1 → none |
| tags: |
added: seg removed: sts sts-rfe |
The workaround used to fix this on OpenStack provider.
1. Add a new interface to your VM:
vi /etc/network/
# The primary network interface
auto juju-br0
iface juju-br0 inet dhcp
bridge_ports eth0
2. In /var/lib/
lxc.network.link = juju-br0
3. Go to your dhcp namespace (sudo ip netns exec
qdhcp-b9c1579d-
3.1 Add the new entries to
/var/lib/
3.2 Restart the dnsmasq process with:
kill -HUP $PID
3.3 Restart the ubuntu hosts that contain the lxcs