© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
@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.