@Kunal Gaurav , This status code only occurs in one of two conditions:
- We’re able to request the instances for the cluster but can’t bootstrap them in time
- We setup the containers on each instance, but can’t start the containers in time
this is an edge case in our service cleanup logic that some containers/clusters might be mis-identified as zombie resources, but there is actually no problem at all, we are working on optimizing the classifying logic and should have a fix deployed soon.
That being said don't hesitate to create an Engineering Support ticket with the workspace id, cluser id and region so databricks can confirm if something similar has happened in the region.
