Failed Tests
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-7nkfq/ha-break-glass-creds-4jtm2 in 3m44s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster ha-break-glass-creds-4jtm2
util.go:3209: Successfully waited for HostedCluster e2e-clusters-7nkfq/ha-break-glass-creds-4jtm2 to have valid conditions in 75ms
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:312: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7nkfq/ha-break-glass-creds-4jtm2 in 50ms
util.go:329: Successfully waited for kubeconfig secret to have data in 50ms
util.go:391: Successfully waited for a successful connection to the guest API server in 25ms
create_cluster_test.go:170: Successfully waited for KAS deployment to have 3 ready replicas in 25ms
create_cluster_test.go:187: fetching mgmt kubeconfig
util.go:312: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-7nkfq/ha-break-glass-creds-4jtm2 in 50ms
util.go:329: Successfully waited for kubeconfig secret to have data in 25ms
control_plane_pki_operator.go:101: generating new break-glass credentials for more than one signer
pki.go:76: loading certificate/key pair from disk for signer customer-break-glass, use $REGENERATE_PKI to generate new ones
control_plane_pki_operator.go:210: creating CSR "2kfjfgz5xalhz5i15dbs00let9mbnejhbpdwduu1bf48" for signer "customer-break-glass", requesting client auth usages
control_plane_pki_operator.go:220: creating CSRA e2e-clusters-7nkfq-ha-break-glass-creds-4jtm2/2kfjfgz5xalhz5i15dbs00let9mbnejhbpdwduu1bf48 to trigger automatic approval of the CSR
control_plane_pki_operator.go:227: Successfully waited for CSR "2kfjfgz5xalhz5i15dbs00let9mbnejhbpdwduu1bf48" to be approved and signed in 3.025s
control_plane_pki_operator.go:139: validating that the client certificate provides the appropriate access
control_plane_pki_operator.go:125: amending the existing kubeconfig to use break-glass client certificate credentials
control_plane_pki_operator.go:142: issuing SSR to identify the subject we are given using the client certificate
control_plane_pki_operator.go:162: ensuring that the SSR identifies the client certificate as having system:masters power and correct username
pki.go:76: loading certificate/key pair from disk for signer sre-break-glass, use $REGENERATE_PKI to generate new ones
control_plane_pki_operator.go:210: creating CSR "1p8zz0t3u8nxfwshsv551q5jh3pyx74pr6mxbnep0nvm" for signer "sre-break-glass", requesting client auth usages
control_plane_pki_operator.go:220: creating CSRA e2e-clusters-7nkfq-ha-break-glass-creds-4jtm2/1p8zz0t3u8nxfwshsv551q5jh3pyx74pr6mxbnep0nvm to trigger automatic approval of the CSR
control_plane_pki_operator.go:227: Successfully waited for CSR "1p8zz0t3u8nxfwshsv551q5jh3pyx74pr6mxbnep0nvm" to be approved and signed in 25ms
control_plane_pki_operator.go:139: validating that the client certificate provides the appropriate access
control_plane_pki_operator.go:125: amending the existing kubeconfig to use break-glass client certificate credentials
control_plane_pki_operator.go:142: issuing SSR to identify the subject we are given using the client certificate
control_plane_pki_operator.go:159: could not send SSR: Post "https://api-ha-break-glass-creds-4jtm2.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-ha-break-glass-creds-4jtm2.aks-e2e.hypershift.azure.devcluster.openshift.com on 172.30.0.10:53: read udp 10.130.172.51:41728->172.30.0.10:53: i/o timeout
hypershift_framework.go:530: Successfully created hostedcluster e2e-clusters-sc4v8/node-pool-2tbzt in 3m38s
hypershift_framework.go:179: Summarizing unexpected conditions for HostedCluster node-pool-2tbzt
util.go:3209: Failed to wait for HostedCluster e2e-clusters-sc4v8/node-pool-2tbzt to have valid conditions in 2s: context deadline exceeded
eventually.go:225: observed *v1beta1.HostedCluster e2e-clusters-sc4v8/node-pool-2tbzt invalid at RV 50887 after 2s:
eventually.go:228: - incorrect condition: wanted ControlPlaneConnectionAvailable=Unknown, got ControlPlaneConnectionAvailable=True: AsExpected(All is well)
eventually.go:228: - incorrect condition: wanted ClusterVersionSucceeding=False, got ClusterVersionSucceeding=True: FromClusterVersion
eventually.go:228: - incorrect condition: wanted ClusterVersionAvailable=False, got ClusterVersionAvailable=True: FromClusterVersion(Done applying 5.1.0-0.ci-2026-08-19-023722-test-ci-op-8qf02i95-latest)
eventually.go:228: - incorrect condition: wanted DataPlaneConnectionAvailable=Unknown, got DataPlaneConnectionAvailable=True: AsExpected(All is well)
eventually.go:228: - incorrect condition: wanted ClusterVersionProgressing=True, got ClusterVersionProgressing=False: FromClusterVersion(Cluster version is 5.1.0-0.ci-2026-08-19-023722-test-ci-op-8qf02i95-latest)
hypershift_framework.go:349: skipping postTeardown()
hypershift_framework.go:327: skipping teardown, already called
util.go:312: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sc4v8/node-pool-2tbzt in 50ms
util.go:329: Successfully waited for kubeconfig secret to have data in 75ms
util.go:391: Successfully waited for a successful connection to the guest API server in 200ms
nodepool_prev_release_test.go:33: Starting NodePoolPrevReleaseCreateTest.
nodepool_test.go:371: Validating CAPI v1 condition message bubbling during machine provisioning
nodepool_test.go:507: CAPI bubbling confirmed for AllNodesHealthy: Status=False, Reason=WaitingForNodeRef
nodepool_test.go:507: CAPI bubbling confirmed for AllMachinesReady: Status=False, Reason=WaitingForInfrastructure
util.go:590: Successfully waited for 1 nodes to become ready for NodePool e2e-clusters-sc4v8/node-pool-2tbzt-x29mp in 12m36.05s
eventually.go:105: Failed to get *v1beta1.NodePool: client rate limiter Wait returned an error: context deadline exceeded
nodepool_test.go:431: Failed to wait for NodePool e2e-clusters-sc4v8/node-pool-2tbzt-x29mp to have correct status in 20m0s: context deadline exceeded
eventually.go:225: observed *v1beta1.NodePool e2e-clusters-sc4v8/node-pool-2tbzt-x29mp invalid at RV 62764 after 20m0s: incorrect condition: wanted SupportedVersionSkew=True, got SupportedVersionSkew=False: UnsupportedSkew(NodePool minor version 4.20 is less than 4.21, which is the minimum NodePool version compatible with the 5.1 HostedCluster)