We also see this behaviour on LXC containers deployed to MAASified machines where MAAS does *not* manage DHCP/DNS.
We are trying to smoosh OpenStack infra into LXC units on MAASified machines for HA. It is most visible with rabbitmq-server, which bails out on NXdomain for the unit. It's also reproducible by just trying to sudo: ubuntu@juju-machine-5-lxc-25:~$ sudo -i sudo: unable to resolve host juju-machine-5-lxc-25 What *could* help is to pre-allocate MACs for each LXC container, either inside or outside MAAS doesn't really matter, and inject them into the host machine via lxc.network.hwaddr, cf. http://manpages.ubuntu.com/manpages/trusty/man5/lxc.container.conf.5.html This would require that cloud-init/juju respect what they get from DHCP/DNS in terms of hostname... ** Attachment added: "rabbitmq-server charm hook error" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1274947/+attachment/4133307/+files/rabbitmq-server-error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1274947 Title: juju lxc instances deployed via MAAS don't have resolvable hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
