PR #7355 - 01-09 19:56

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
31m21.18s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-6rrqx/autoscaling-xn4b2 in 2m14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-xn4b2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-6rrqx/autoscaling-xn4b2 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
17m52.41s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6rrqx/autoscaling-xn4b2 in 2m48.05s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-xn4b2.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-autoscaling-xn4b2.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 18.425s util.go:565: Successfully waited for 1 nodes to become ready in 11m6.025s util.go:598: Successfully waited for HostedCluster e2e-clusters-6rrqx/autoscaling-xn4b2 to rollout in 3m33.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-6rrqx/autoscaling-xn4b2 to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
350ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-6rrqx/autoscaling-xn4b2 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-75bdcc8c7f-qsnjm has a restartCount > 0 (5)
TestAzureScheduler
32m36.54s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zrlwb/azure-scheduler-26t77 in 2m30s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-26t77 util.go:2949: Successfully waited for HostedCluster e2e-clusters-zrlwb/azure-scheduler-26t77 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
18m59.35s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zrlwb/azure-scheduler-26t77 in 3m0.05s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-azure-scheduler-26t77.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-26t77.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-azure-scheduler-26t77.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 43.5s util.go:565: Successfully waited for 2 nodes to become ready in 11m27.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-zrlwb/azure-scheduler-26t77 to rollout in 3m42.075s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zrlwb/azure-scheduler-26t77 to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zrlwb/azure-scheduler-26t77 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-7b4656454f-r6dxd has a restartCount > 0 (6)
TestCreateCluster
31m9.67s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-s7wfm/create-cluster-69lzx in 2m14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-69lzx util.go:2949: Successfully waited for HostedCluster e2e-clusters-s7wfm/create-cluster-69lzx to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
18m23.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s7wfm/create-cluster-69lzx in 2m42.05s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-69lzx.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-create-cluster-69lzx.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.325s util.go:565: Successfully waited for 2 nodes to become ready in 10m33.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-s7wfm/create-cluster-69lzx to rollout in 4m36.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-s7wfm/create-cluster-69lzx to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
190ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s7wfm/create-cluster-69lzx 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-556f778b5c-6xknq has a restartCount > 0 (6)
TestCreateClusterCustomConfig
34m23.29s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-4msrh/custom-config-jgb4d in 2m15s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-jgb4d util.go:2949: Successfully waited for HostedCluster e2e-clusters-4msrh/custom-config-jgb4d to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
21m55.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4msrh/custom-config-jgb4d in 2m39.05s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-jgb4d.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 1m0.425s util.go:565: Successfully waited for 2 nodes to become ready in 10m42.1s util.go:598: Successfully waited for HostedCluster e2e-clusters-4msrh/custom-config-jgb4d to rollout in 7m27.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-4msrh/custom-config-jgb4d to have valid conditions in 50ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-4msrh/custom-config-jgb4d 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-688d4f85cd-sdzff has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
26m35.5s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qrp4w/node-pool-lczr8 in 2m4s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-lczr8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-qrp4w/node-pool-lczr8 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
13m31.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qrp4w/node-pool-lczr8 in 2m48.05s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-lczr8.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-node-pool-lczr8.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.55s util.go:565: Successfully waited for 0 nodes to become ready in 100ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-qrp4w/node-pool-lczr8 to have valid conditions in 10m6.075s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
230ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qrp4w/node-pool-lczr8 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-8586f889dc-2rnh6 has a restartCount > 0 (3)
TestNodePool/HostedCluster2
26m41.85s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-fzjzg/node-pool-g2lk6 in 2m12s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-g2lk6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-fzjzg/node-pool-g2lk6 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
13m28.2s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fzjzg/node-pool-g2lk6 in 2m39.075s util.go:301: Successfully waited for kubeconfig secret to have data in 50ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-g2lk6.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.225s util.go:565: Successfully waited for 0 nodes to become ready in 225ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-fzjzg/node-pool-g2lk6 to have valid conditions in 10m12.075s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
230ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-fzjzg/node-pool-g2lk6 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-578ff7448d-bwvd5 has a restartCount > 0 (3)
TestUpgradeControlPlane
1h6m25.77s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-tm64446s/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-tm64446s/release@sha256:50365db2594de25387ca67b64923a54c986224e6baee868a768dcaac1e2bc1cf hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-jzggb/control-plane-upgrade-rcn2c in 2m11s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-rcn2c util.go:2949: Successfully waited for HostedCluster e2e-clusters-jzggb/control-plane-upgrade-rcn2c to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m1.66s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jzggb/control-plane-upgrade-rcn2c in 50ms 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 50ms control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-tm64446s/release@sha256:50365db2594de25387ca67b64923a54c986224e6baee868a768dcaac1e2bc1cf util.go:598: Successfully waited for HostedCluster e2e-clusters-jzggb/control-plane-upgrade-rcn2c to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
220ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-jzggb/control-plane-upgrade-rcn2c 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-5db6c5fcfc-n6nj8 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-jzggb-control-plane-upgrade-rcn2c/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-jzggb-control-plane-upgrade-rcn2c/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)