Need to investigate Alibaba VM provisioning error from CB-Spider #2131
Description
What happened
During Alibaba VM provisioning, I've got following error situation frequently.
CB-Spider internally rollback VM, and CB-TB does not react for the situation correctly. (just rely on timeout)
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:13 VMHandler.go:494, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).StartVM() - After waiting for a long time, the status of the created VM did not change to [Running], so the process is being terminated.
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:13 VMHandler.go:615, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).WaitForRun() - Forcing termination as the VM status remains unchanged as [%!s(int=120)] even after waiting for a long time (%!d(string=Running) seconds).
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:13 VMHandler.go:494, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).StartVM() - After waiting for a long time, the status of the created VM did not change to [Running], so the process is being terminated.
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:19 VMHandler.go:615, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).WaitForRun() - Forcing termination as the VM status remains unchanged as [%!s(int=120)] even after waiting for a long time (%!d(string=Running) seconds).
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:19 VMHandler.go:494, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).StartVM() - After waiting for a long time, the status of the created VM did not change to [Running], so the process is being terminated.
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:19 VMHandler.go:615, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).WaitForRun() - Forcing termination as the VM status remains unchanged as [%!s(int=120)] even after waiting for a long time (%!d(string=Running) seconds).
cb-spider | [CB-SPIDER].[ERROR]: 2025-09-02 16:28:19 VMHandler.go:494, github.com/cloud-barista/cb-spider/cloud-control-manager/cloud-driver/drivers/alibaba/resources.(*AlibabaVMHandler).StartVM() - After waiting for a long time, the status of the created VM did not change to [Running], so the process is being terminated.
How to reproduce it (as minimally and precisely as possible)
ecs.t6-c4m1.large (2vCPU, 0.5GB)
ecs.t6-c2m1.large (2vCPU, 1GB)
ecs.t6-c1m1.large (2vCPU, 2GB)
ecs.t6-c1m2.large (2vCPU, 4GB)
ecs.t6-c1m4.large (2vCPU, 8GB)
ecs.t6-c1m4.xlarge (4vCPU, 16GB)
"imageId": "ubuntu_22_04_x64_20G_alibase_20250722.vhd",