This is a cloud-init problem I think. Basically when the container first starts it's got the default hostname from the image "ubuntu", then it runs dhclient to get an IP, that dhclient calls sends the hostname to dnsmasq "ubuntu" at that point, then cloud-init runs and sets the right hostname, but it doesn't re- trigger dhclient so the hostname is never updated on the DHCP server side.
The next time the container boots, things are fixed, but that's not exactly ideal. ** Package changed: lxd (Ubuntu) => cloud-init (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574963 Title: juju2 lxd launch hostname reverse lookup inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1574963/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
