Better UX to indicate the reason of WaitingForInfrastructure when using MachinePool/AzureMachinePool #4964
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
/kind bug
What steps did you take and what happened:
Add a
AzureMachinePool
to a cluster with avmSize
not available in theMachinePool
specifiedfailureDomains
.While monitor the advancement of the pool provisionning with
clusterctl
, I've noticed that the state was not changing and staying blocked onWaitingForInfrastructure
Describing both MachinePool and AzureMachinePool object gave me no indication that the chosen
vmSize
was not available in the region/zones I've specified.Finding the problem required me to check the logs of
capz
controller.What did you expect to happen:
Have a better explanation on the status of the object to know why we're
WaitingForInfrastructure
.Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
)/etc/os-release
): Ubuntu 22.04The text was updated successfully, but these errors were encountered: