PR #7429 - 01-09 07:06

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
36m32.04s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-dp7n8/autoscaling-szx4m in 2m32s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-szx4m util.go:2949: Successfully waited for HostedCluster e2e-clusters-dp7n8/autoscaling-szx4m to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
22m20.95s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dp7n8/autoscaling-szx4m in 3m15.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-szx4m.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 14.35s util.go:565: Successfully waited for 1 nodes to become ready in 10m27.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-dp7n8/autoscaling-szx4m to rollout in 8m18.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-dp7n8/autoscaling-szx4m to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
160ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dp7n8/autoscaling-szx4m 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-57d598f849-75zcm has a restartCount > 0 (6)
TestAzureScheduler
34m52.36s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-46scw/azure-scheduler-vg6s9 in 2m28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-vg6s9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-46scw/azure-scheduler-vg6s9 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
22m24.01s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-46scw/azure-scheduler-vg6s9 in 3m6.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-vg6s9.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": net/http: TLS handshake timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-vg6s9.aks-e2e.hypershift.azure.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": EOF util.go:363: Successfully waited for a successful connection to the guest API server in 26.5s util.go:565: Successfully waited for 2 nodes to become ready in 10m39.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-46scw/azure-scheduler-vg6s9 to rollout in 8m6.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-46scw/azure-scheduler-vg6s9 to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
150ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-46scw/azure-scheduler-vg6s9 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-6fb8d8f6c4-k8stm has a restartCount > 0 (6)
TestCreateCluster
36m30.23s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bsttj/create-cluster-n9wbq in 2m33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-n9wbq util.go:2949: Successfully waited for HostedCluster e2e-clusters-bsttj/create-cluster-n9wbq to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
22m31.78s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bsttj/create-cluster-n9wbq 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-n9wbq.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 25.225s util.go:565: Successfully waited for 2 nodes to become ready in 10m24.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-bsttj/create-cluster-n9wbq to rollout in 8m33.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-bsttj/create-cluster-n9wbq to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
160ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bsttj/create-cluster-n9wbq 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-5448bc4c75-vns8k has a restartCount > 0 (7)
TestCreateClusterCustomConfig
35m16.87s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-8lfxg/custom-config-lb6hk in 2m27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-lb6hk util.go:2949: Successfully waited for HostedCluster e2e-clusters-8lfxg/custom-config-lb6hk to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
22m1.85s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8lfxg/custom-config-lb6hk in 2m57.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-custom-config-lb6hk.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 40.25s util.go:565: Successfully waited for 2 nodes to become ready in 10m57.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-8lfxg/custom-config-lb6hk to rollout in 7m21.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-8lfxg/custom-config-lb6hk to have valid conditions in 25ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-8lfxg/custom-config-lb6hk 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-6bc5d55d89-s2m5b has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
25m11.85s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-sm687/node-pool-fs4gm in 2m33s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-fs4gm util.go:2949: Successfully waited for HostedCluster e2e-clusters-sm687/node-pool-fs4gm to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
12m41.61s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sm687/node-pool-fs4gm 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-node-pool-fs4gm.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 17.275s util.go:565: Successfully waited for 0 nodes to become ready in 50ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-sm687/node-pool-fs4gm to have valid conditions in 9m15.075s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-sm687/node-pool-fs4gm 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-5985b544c5-mqcf6 has a restartCount > 0 (4)
TestNodePool/HostedCluster2
25m8.05s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-brl66/node-pool-7c5lw in 2m25s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-7c5lw util.go:2949: Successfully waited for HostedCluster e2e-clusters-brl66/node-pool-7c5lw to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
12m57.57s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-brl66/node-pool-7c5lw in 3m6.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-7c5lw.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 30.25s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-brl66/node-pool-7c5lw to have valid conditions in 9m15.075s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-brl66/node-pool-7c5lw 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-7bc5bdc4c6-x7dct has a restartCount > 0 (1)
TestUpgradeControlPlane
1h3m37.24s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-9wz43jbk/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-9wz43jbk/release@sha256:121f29272494e050eac6d93e6a7c4065dfe746add0548eb8f93ad50fbba53946 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-28x6s/control-plane-upgrade-bz78r in 2m34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-bz78r util.go:2949: Successfully waited for HostedCluster e2e-clusters-28x6s/control-plane-upgrade-bz78r to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m1.34s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-28x6s/control-plane-upgrade-bz78r in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 25ms 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-9wz43jbk/release@sha256:121f29272494e050eac6d93e6a7c4065dfe746add0548eb8f93ad50fbba53946 util.go:598: Successfully waited for HostedCluster e2e-clusters-28x6s/control-plane-upgrade-bz78r to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-28x6s/control-plane-upgrade-bz78r 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-89c6d6554-zhzwf 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-28x6s-control-plane-upgrade-bz78r/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-28x6s-control-plane-upgrade-bz78r/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)