Public bug reported: Hi,
Using manual provider on top of VMWare. Juju: 2.9.14 VM: Focal Containers: Bionic I've noticed that, in a given Focal host, 2x Bionic containers may have different behavior: one successfully completes cloud-init whereas the other fails. The failed container errors at "apt update" in cloud-init with: Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease Something wicked happened resolving 'PROXY_IP:<PORT>' (-9 - Address family for hostname not supported) (Likely this is the line where it breaks: https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436) Failed container, full cloud-init-output.log: https://pastebin.canonical.com/p/hKNw49mvJP/ Successful container, full cloud-init-output.log: https://pastebin.canonical.com/p/P6MZdQPrWd/ Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/ I can see that, on the host, dnsmasq served the FAN IP to the broken container after the "apt-update" was called. ----- FAILED CONTAINER -----: Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.198 00:16:3e:da:dd:c4 apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:02:13 +0000. Up 3.90 seconds. ----- SUCCESSFUL CONTAINER -----: Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 252.252.15.253 00:16:3e:d7:6b:ef apt-update on cloud-init was ran: Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at Sun, 19 Sep 2021 13:10:10 +0000. Up 35.99 seconds. In the case of the Failed Container, the DHCPOFFER arrived 1s after the "apt update" was requested, whereas the Successful Container logged a DHCPOFFER 30s before the "apt update". ** Affects: charm-rabbitmq-server Importance: Undecided Status: New ** Affects: juju Importance: Undecided Status: New ** Affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-fan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944080 Title: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
