Removing a container does not remove the underlying MAAS device representing the container unless the host is also removed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Christian Muirhead |
Bug Description
It does not remove the DHCP and DNS configurations on MAAS after juju removes LXD container(machine).
dpkg -l '*maas*' | cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.0.0~beta5+
ii maas-cli 2.0.0~beta5+
un maas-cluster-
ii maas-common 2.0.0~beta5+
ii maas-dhcp 2.0.0~beta5+
ii maas-dns 2.0.0~beta5+
ii maas-proxy 2.0.0~beta5+
ii maas-rack-
ii maas-region-api 2.0.0~beta5+
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.0.0~beta5+
ii python3-maas-client 2.0.0~beta5+
ii python3-
dpkg -l '*juju*' | cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii juju 2.0-beta7-
ii juju-2.0 2.0-beta7-
un juju-core <none> <none> (no description available)
un juju2 <none> <none> (no description available)
juju add-machine --constraints spaces=
juju show-machine
model: default
machines:
"0":
juju-status:
current: started
since: 25 May 2016 18:30:08+09:00
version: 2.0-beta7
dns-name: 10.192.228.52
instance-id: 4y3h7p
machine-status:
current: running
message: Deployed
since: 25 May 2016 18:28:54+09:00
series: xenial
containers:
0/lxd/3:
current: started
since: 26 May 2016 11:19:10+09:00
version: 2.0-beta7
dns-name: 10.192.228.56
current: running
message: Container started
since: 26 May 2016 11:18:19+09:00
series: xenial
hardware: arch=amd64 cpu-cores=24 mem=128825M availability-
# On the physical node
sudo lxc list
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| juju-machine-
| | | 192.168.101.56 (eth1) | | | |
| | | 192.168.102.56 (eth2) | | | |
| | | 10.192.229.56 (eth3) | | | |
+------
juju remove-machine 0/lxd/3
juju show-machine
model: default
machines:
"0":
juju-status:
current: started
since: 25 May 2016 18:30:08+09:00
version: 2.0-beta7
dns-name: 10.192.228.52
instance-id: 4y3h7p
machine-status:
current: running
message: Deployed
since: 25 May 2016 18:28:54+09:00
series: xenial
hardware: arch=amd64 cpu-cores=24 mem=128825M availability-
dig -x 10.192.228.56
; <<>> DiG 9.10.3-P4-Ubuntu <<>> -x 10.192.228.56
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59606
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 2
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;56.228.
;; ANSWER SECTION:
56.228.
56.228.
;; AUTHORITY SECTION:
228.192.
;; ADDITIONAL SECTION:
rnd.example.net. 30 IN A 10.192.228.2
;; Query time: 0 msec
;; SERVER: 10.192.
;; WHEN: Thu May 26 14:30:31 KST 2016
;; MSG SIZE rcvd: 154
# on the maas node
cat /etc/bind/
unmordant-shandra 30 IN A 10.192.228.56
cat /var/lib/
...
...
host 00-16-3e-b0-82-7a {
#
# Node DHCP snippets
#
hardware ethernet 00:16:3e:b0:82:7a;
fixed-address 10.192.228.56;
}
Changed in juju-core: | |
milestone: | none → 2.0-beta9 |
tags: | added: hours maas-provider network reliability |
Changed in juju-core: | |
milestone: | 2.0-beta9 → 2.0-beta10 |
Changed in juju-core: | |
milestone: | 2.0-beta10 → 2.0-beta11 |
Changed in juju-core: | |
milestone: | 2.0-beta11 → 2.0-beta12 |
tags: | added: 2.0 |
Changed in juju-core: | |
milestone: | 2.0-beta12 → 2.0-beta13 |
Changed in juju-core: | |
assignee: | nobody → Christian Muirhead (2-xtian) |
Changed in juju-core: | |
milestone: | 2.0-beta13 → 2.0-beta14 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0-beta16 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta16 → none |
milestone: | none → 2.0-beta16 |
Changed in juju: | |
milestone: | 2.0-beta16 → 2.0-beta17 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Juju registers each container into MAAS as a multi-NIC device with a parent set to its host instance. It's up to MAAS to clean up those settings after the device representing the container is gone along with its host.