I rebooted our VM over 60 times today without any further issues. Since the VM network went down before I restarted the VM or lost access to the serial console login, I'm also thinking now it was a network issue to begin with. It could always be coincidence that I was able to get the VM back by force stopping and then starting the vm from a stopped state, when neither restarting nor redeploying helped, but there is one thing, correct me if this is wrong, that is different about force stopping and that is it deallocates the VM. If the network issue were internal to the VM I wonder if both restarting and redeploying could have with the best of intentions persisted the faulty network state to the point where the operations failed, while dealocating ended the issue and the VM was able to start over clean.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
