Comment 2 for bug 928521

That's a good point. I can confirm the instance was still running fine, just with the original instance type (as expected). It does seem odd to move to ERROR if it's still running. I think moving back to ACTIVE and adding an asynchronous fault would make most sense.