Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/2439
** Bug watch added: github.com/canonical/cloud-init/issues #2439 https://github.com/canonical/cloud-init/issues/2439 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1303925 Title: commissioning fails silently if a node can't reach the region controller Status in cloud-init: Expired Status in MAAS: Fix Released Bug description: We recently had a node which completely refused to commission in MAAS. After (literally) several man days of debugging, we figured out that it was because the node couldn't talk to the region controller over HTTP. Obviously, that's ultimately our mistake/problem, but MAAS could have been a lot better at helping us to help ourselves; currently, there's absolutely no indication from the boot process that the HTTP connection to the region controller is the problem. Attached is the serial console output (from the point of boot) for the node that was failing to commission. 91.189.94.35 is the MAAS region controller and 91.189.88.20 is the MAAS cluster controller. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1303925/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
