PR #7430 - 01-09 07:05

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
31m39.53s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zwjl5/autoscaling-5vchx in 2m20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-5vchx util.go:2949: Successfully waited for HostedCluster e2e-clusters-zwjl5/autoscaling-5vchx to have valid conditions in 25ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
19m9.11s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zwjl5/autoscaling-5vchx in 2m39.075s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-5vchx.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-5vchx.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 41.45s util.go:565: Successfully waited for 1 nodes to become ready in 10m30.025s util.go:598: Successfully waited for HostedCluster e2e-clusters-zwjl5/autoscaling-5vchx to rollout in 5m12.025s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zwjl5/autoscaling-5vchx to have valid conditions in 25ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
150ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zwjl5/autoscaling-5vchx in 25ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms util.go:782: Container controller in pod cloud-network-config-controller-5d7d8c89ff-pcc4v has a restartCount > 0 (6)
TestAzureScheduler
32m57.51s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-75q4c/azure-scheduler-f2msk in 2m5s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-f2msk util.go:2949: Successfully waited for HostedCluster e2e-clusters-75q4c/azure-scheduler-f2msk to have valid conditions in 25ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
18m56.82s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-75q4c/azure-scheduler-f2msk in 3m3.05s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-f2msk.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 32.3s util.go:565: Successfully waited for 2 nodes to become ready in 11m15.1s util.go:598: Successfully waited for HostedCluster e2e-clusters-75q4c/azure-scheduler-f2msk to rollout in 4m0.025s util.go:2949: Successfully waited for HostedCluster e2e-clusters-75q4c/azure-scheduler-f2msk to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
170ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-75q4c/azure-scheduler-f2msk in 25ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms util.go:782: Container controller in pod cloud-network-config-controller-856fbf6999-gds47 has a restartCount > 0 (6)
TestCreateCluster
30m18.26s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-85jw7/create-cluster-ncfb5 in 2m16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-ncfb5 util.go:2949: Successfully waited for HostedCluster e2e-clusters-85jw7/create-cluster-ncfb5 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
17m31.81s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-85jw7/create-cluster-ncfb5 in 3m3.05s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-ncfb5.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 19.275s util.go:565: Successfully waited for 2 nodes to become ready in 10m30.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-85jw7/create-cluster-ncfb5 to rollout in 3m33.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-85jw7/create-cluster-ncfb5 to have valid conditions in 25ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-85jw7/create-cluster-ncfb5 in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms util.go:782: Container controller in pod cloud-network-config-controller-7cdfb55bb7-v5wfc has a restartCount > 0 (5)
TestCreateClusterCustomConfig
34m7.35s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-rbjbq/custom-config-gr4qn in 2m17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-gr4qn util.go:2949: Successfully waited for HostedCluster e2e-clusters-rbjbq/custom-config-gr4qn to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
21m56.79s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rbjbq/custom-config-gr4qn in 2m57.025s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-gr4qn.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 32.35s util.go:565: Successfully waited for 2 nodes to become ready in 11m6.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-rbjbq/custom-config-gr4qn to rollout in 7m15.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-rbjbq/custom-config-gr4qn to have valid conditions in 25ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
170ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rbjbq/custom-config-gr4qn in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms util.go:782: Container controller in pod cloud-network-config-controller-6f8dd6c57f-ccv2k has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
24m57.74s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-b6dct/node-pool-zkbp2 in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-zkbp2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-b6dct/node-pool-zkbp2 to have valid conditions in 25ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
13m4.08s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b6dct/node-pool-zkbp2 in 2m45.05s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-zkbp2.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 21.175s util.go:565: Successfully waited for 0 nodes to become ready in 50ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-b6dct/node-pool-zkbp2 to have valid conditions in 9m51.05s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b6dct/node-pool-zkbp2 in 75ms util.go:301: Successfully waited for kubeconfig secret to have data in 50ms util.go:782: Container controller in pod cloud-network-config-controller-5bcb54c7bc-dv2zl has a restartCount > 0 (2)
TestNodePool/HostedCluster2
25m2.62s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-79rhf/node-pool-rg79w in 2m21s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-rg79w util.go:2949: Successfully waited for HostedCluster e2e-clusters-79rhf/node-pool-rg79w to have valid conditions in 25ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
13m9.78s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-79rhf/node-pool-rg79w in 2m48.075s util.go:301: Successfully waited for kubeconfig secret to have data in 25ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-rg79w.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout util.go:363: Successfully waited for a successful connection to the guest API server in 21.225s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-79rhf/node-pool-rg79w to have valid conditions in 9m54.075s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
190ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-79rhf/node-pool-rg79w in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 50ms util.go:782: Container controller in pod cloud-network-config-controller-bbfd47958-dlz4g has a restartCount > 0 (3)
TestUpgradeControlPlane
1h1m21.06s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:1c5d76ff3d6fd87e77b6991ebe9bb96e7b2328ae7db8e00f488af6bbc6d7e877 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bkl4w/control-plane-upgrade-hcm7t in 2m16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-hcm7t util.go:2949: Successfully waited for HostedCluster e2e-clusters-bkl4w/control-plane-upgrade-hcm7t to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m1.52s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bkl4w/control-plane-upgrade-hcm7t in 25ms util.go:301: Successfully waited for kubeconfig secret to have data in 50ms util.go:363: Successfully waited for a successful connection to the guest API server in 25ms control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-4pp7261g/release@sha256:1c5d76ff3d6fd87e77b6991ebe9bb96e7b2328ae7db8e00f488af6bbc6d7e877 util.go:598: Successfully waited for HostedCluster e2e-clusters-bkl4w/control-plane-upgrade-hcm7t to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bkl4w/control-plane-upgrade-hcm7t in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms util.go:782: Container controller in pod cloud-network-config-controller-788c6f9d78-28mkk has a restartCount > 0 (9)
TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
30m0s
eventually.go:258: Failed to get **v1beta1.ControlPlaneComponent: client rate limiter Wait returned an error: context deadline exceeded util.go:638: Failed to wait for control plane components to complete rollout in 30m0s: context deadline exceeded eventually.go:383: observed invalid **v1beta1.ControlPlaneComponent state after 30m0s eventually.go:400: - observed **v1beta1.ControlPlaneComponent e2e-clusters-bkl4w-control-plane-upgrade-hcm7t/cluster-network-operator invalid: incorrect condition: wanted RolloutComplete=True, got RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready) util.go:638: *v1beta1.ControlPlaneComponent e2e-clusters-bkl4w-control-plane-upgrade-hcm7t/cluster-network-operator conditions: util.go:638: Available=True: AsExpected(Deployment cluster-network-operator is available) util.go:638: RolloutComplete=False: WaitingForOperands(deployment cloud-network-config-controller is not ready)