Open
Description
Describe the bug
https://github.com/kubestellar/ocm-status-addon/actions/runs/9308229088 failed but the equivalent https://github.com/kubestellar/ocm-status-addon/actions/runs/9308567124 succeeded.
Steps To Reproduce
Try the E2E test many times.
Expected Behavior
Consistency.
Additional Context
In test/e2e/setup-ocm-and-addon.sh,
kubectl --context kind-hub -n open-cluster-management-hub wait --for=condition=available deploy cluster-manager-registration-controller --timeout=60s
happens before it is guaranteed that said Deployment object even exists (and kubectl wait immediately fails if the object does not exist).
BTW, why is this part of the function for create_and_register a new cluster, rather than something that follows clusteradm init ?