hypershift_framework.go:316: Successfully created hostedcluster e2e-clusters-stnrl/azure-scheduler-rwn9j in 2m16s
hypershift_framework.go:115: Summarizing unexpected conditions for HostedCluster azure-scheduler-rwn9j
util.go:2123: Successfully waited for HostedCluster e2e-clusters-stnrl/azure-scheduler-rwn9j to have valid conditions in 25ms
hypershift_framework.go:194: skipping postTeardown()
hypershift_framework.go:175: skipping teardown, already called
util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-stnrl/azure-scheduler-rwn9j in 25ms
util.go:235: Successfully waited for kubeconfig secret to have data in 25ms
util.go:281: Successfully waited for a successful connection to the guest API server in 25ms
util.go:462: Successfully waited for 2 nodes to become ready in 25ms
azure_scheduler_test.go:111: Updated clusterSizingConfig.
azure_scheduler_test.go:158: Successfully waited for HostedCluster size label and annotations updated in 50ms
azure_scheduler_test.go:150: Scaled Nodepool. Namespace: e2e-clusters-stnrl, name: azure-scheduler-rwn9j, replicas: 0xc0029de57c
eventually.go:258: Failed to get **v1.Node: context deadline exceeded
util.go:462: Failed to wait for 3 nodes to become ready in 30m0s: context deadline exceeded
eventually.go:383: observed invalid **v1.Node state after 30m0s
eventually.go:400: - observed **v1.Node collection invalid: expected 3 nodes, got 2