firesphere
indy

@stevie Just saw the alert about the failed deployment, as that error was coming from the "bake" stage it didn't have anything to do with you current deployment. Basically a deployment will wait for any existing scaling operations to complete before it does anything, in your case an unhealthy server was being taken out of service (fairly common) just as you were trying to deploy.

All instances are healthy now so try another deployment.

firesphere

Either way, if one of the VMs isn't healthy, it means data might get lost => P1/P2

null

especially if the site is generating revenue