Thanks for this bug report, this all now makes sense why an instance was unexpectedly powered off when we took back a previously evacuated compute node.
I spent about 2 hours walking through the lifecycle events and power state sync code trying to find what caused this exact issue.
Thanks for this bug report, this all now makes sense why an instance was unexpectedly powered off when we took back a previously evacuated compute node.
I spent about 2 hours walking through the lifecycle events and power state sync code trying to find what caused this exact issue.