@mahmoh I had a similar issue in the QA lab, where just one of the nodes exhibited the symptom described here (hostname set to "connection timeout"). It turned out I had another DHCP server (different from the cluster controller configured one) running on that subnet and causing this odd behavior.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas-enlist in Ubuntu. https://bugs.launchpad.net/bugs/1081660 Title: If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
