Howdy; Getting repeated Failed due to unhealthy allocations error on deployment with a minor change that builds and runs locally. Maybe in the yyz region as it looks like ORD comes up healthy before bailing. v74 is being deployed 9334aef6: ord pending 9334aef6: ord pending 9334aef6: ord runnin…

This appears to have happened because the previous VM didn’t actually shut down, and the new one couldn’t grab the IP and volume. We have a check for this that didn’t catch it for some reason, sorry about that. I cleaned it up and you’re good to go now.

Failed due to unhealthy allocations - rolling back

Questions / Help

eyepulp October 15, 2021, 10:55pm 5

I’ve passive-aggressively marked you making the fix as the right solution, because laziness. =)

deploy failed due to unhealthy allocations

Topic		Replies	Views
Deploy error - Failed due to unhealthy allocations Questions / Help	3	1198	October 18, 2021
Failed due to unhealthy allocations - not rolling back to stable job version 6 as current job has same specification and deploying as v7	3	596	February 9, 2023
Deployment Errors - Failed due to unhealthy allocations Build debugging	9	1758	October 10, 2021
Failed due to unhealthy allocations - no stable job version to auto revert	2	436	April 11, 2023
deploys failing due to "unhealthy allocations" Questions / Help	4	2070	October 26, 2022

Failed due to unhealthy allocations - rolling back

Related topics