** No longer affects: maas/3.3
--
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/1910552
Title:
machines fail to boot if MAAS doesn't respond to cloud-init
Status in cloud-init:
Fix Released
Status in MAAS:
Triaged
Bug description:
We have a recurring issue on a MAAS 2.3.7 (xenial), where once in a while we
need to restart rackd and regiond to make maas respond to machines rebooting.
This itself would be a different bug though.
What I'd like to report here is that a machine should be able to finish its
boot sequence even if it can't talk to the MAAS API.
Observed behaviour:
[ OK ] Started Raise network interfaces.
[ OK ] Reached target Network.
Starting Initial cloud-init job (metadata service crawler)...
(stuck here indefinitely)
(restart rackd and regiond)
the machine reboots successfully.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1910552/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
