lxd containers fail to get IP address assigned when created by Juju
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned | ||
2.4 |
New
|
Undecided
|
Unassigned |
Bug Description
Using Juju 2.4.1-bionic-amd64 on a Openstack-
Deployment current status: https:/
Cloud-init is failing to run on Juju-created LXD containers:
https:/
Running dhclient on one of the containers get an IP which is not related to fan-networking.
Containers manually created using LXC are working (although they do not use fan-networking).
Similar bugs have been reported:
https:/
https:/
As suggested on Bug 1762700, comment #26:
/var/lib/
Returns:
network:
config: "disabled"
ip addr list on one of the containers return:
root@juju-
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
14: eth0@if15: <BROADCAST,
link/ether 00:16:3e:e5:7e:19 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::216:
valid_lft forever preferred_lft forever
16: eth1@if17: <BROADCAST,
link/ether 00:16:3e:aa:13:66 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::216:
valid_lft forever preferred_lft forever
juju crashdump -m default fails with:
Command "timeout 45s juju run --all 'sh -c "sudo find /etc/alternatives /etc/ceph /etc/cinder /etc/glance /etc/keystone /etc/netplan /etc/network /etc/neutron /etc/nova /etc/quantum /etc/swift /opt/nedge/var/log /run/cloud-init /usr/share/
Command "juju scp 4/lxd/0:
Command "tar -pxf 4efcde4c-
Command "rm 4efcde4c-
Changed in juju: | |
milestone: | none → 2.5-beta1 |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: lxd |
Bug https:/ /bugs.launchpad .net/juju/ +bug/1762700, was caused by a error in a juju script: /etc/network/ interfaces. py. See #18 for more info. Do you see errors related to interfaces.py in the logs in this case? There were some overlapping cloud init issues there, not sure if they go resolved, but unrelated to the juju piece of the bug.
It looks like 1756040 should be still marked against 2.4, on the cloudinit piece, could you please provide the data per #6? That cloudinit trace keeps happening and we should really get that thing resolved.