I've been running this for 3+ days now and cannot reproduce this specific issue. From the look of the error it appears to be a hardware related NMI issue, so perhaps we have some faulty H/W in this specific case.
When running these tests for several days now with and without the kernel parameters I have observed the following: 1. It can take >10-15 minutes for a reboot. 2. Our instances were being accidentally deleted by a jenkins job which could be a reason why some of our original assumptions that the VM had died on reboot were incorrect. 3. When rebooting almost immediately when ssh access becomes available reboot gets stuck with systemd issues: sudo reboot systemctl status reboot.target Failed to get properties: Connection timed out and the only way to reboot is using the following: sudo systemctl --force reboot This could also be a reason why the automated reboot testing got locked up and we mistakenly believed that reboots were failing due to H/W issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822175 Title: i3.metal flavour type fails to respond after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
