Comment 6 for bug 1437201

(noting just in case people jump to this comment, my report was only tested on Juno, not Kilo, if you're busy with releasing please ignore)

Thanks for looking into things Angus.

Is that what you get on master for INFO, or DEBUG?

If it's DEBUG, does that mean there's no log for this situation in info?

If I remember correctly, heat will kill a VM that has failed to schedule and try again. In this case, probably there should be a line saying "I'm trying to start a new stack, and the VM I started up failed to schedule within my timeout"...