PR #6827 - 09-15 15:06

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

264
Total Tests
235
Passed
7
Failed
22
Skipped

Failed Tests

TestAzureScheduler
32m47.91s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-wkhgf/azure-scheduler-ppdzh in 2m37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-ppdzh util.go:2721: Successfully waited for HostedCluster e2e-clusters-wkhgf/azure-scheduler-ppdzh to have valid conditions in 50ms hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
18m19.81s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wkhgf/azure-scheduler-ppdzh in 3m9.05s util.go:276: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-ppdzh.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:330: Successfully waited for a successful connection to the guest API server in 13.2s util.go:513: Successfully waited for 2 nodes to become ready in 11m3.075s util.go:546: Successfully waited for HostedCluster e2e-clusters-wkhgf/azure-scheduler-ppdzh to rollout in 3m48.05s util.go:2721: Successfully waited for HostedCluster e2e-clusters-wkhgf/azure-scheduler-ppdzh to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-wkhgf/azure-scheduler-ppdzh in 50ms util.go:276: Successfully waited for kubeconfig secret to have data in 50ms util.go:755: Container control-plane-operator in pod control-plane-operator-5fdf7f6c66-6gj4w has a restartCount > 0 (1)
TestNodePool
0s
TestNodePool/HostedCluster0
24m13.74s
hypershift_framework.go:396: Successfully created hostedcluster e2e-clusters-pzslc/node-pool-qjm9f in 2m37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-qjm9f util.go:2721: Successfully waited for HostedCluster e2e-clusters-pzslc/node-pool-qjm9f to have valid conditions in 50ms hypershift_framework.go:239: skipping postTeardown() hypershift_framework.go:220: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
11m12.52s
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pzslc/node-pool-qjm9f in 3m0.05s util.go:276: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-qjm9f.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:330: Successfully waited for a successful connection to the guest API server in 20.2s util.go:513: Successfully waited for 0 nodes to become ready in 75ms util.go:2721: Successfully waited for HostedCluster e2e-clusters-pzslc/node-pool-qjm9f to have valid conditions in 7m45.05s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:259: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pzslc/node-pool-qjm9f in 50ms util.go:276: Successfully waited for kubeconfig secret to have data in 50ms util.go:755: Container control-plane-operator in pod control-plane-operator-65fdc484b4-cqb4w has a restartCount > 0 (1)