PR #7139 - 01-09 16:41

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
32m54.82s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5xchh/autoscaling-m5jb7 in 2m23s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-m5jb7 util.go:2949: Successfully waited for HostedCluster e2e-clusters-5xchh/autoscaling-m5jb7 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
19m24.99s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5xchh/autoscaling-m5jb7 in 2m51.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-m5jb7.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 1 nodes to become ready in 10m48.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-5xchh/autoscaling-m5jb7 to rollout in 5m9.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-5xchh/autoscaling-m5jb7 to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5xchh/autoscaling-m5jb7 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-746f9bfd7b-tzdgx has a restartCount > 0 (6)
TestAzureScheduler
30m51.89s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-ls792/azure-scheduler-sm26h in 2m19s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-sm26h util.go:2949: Successfully waited for HostedCluster e2e-clusters-ls792/azure-scheduler-sm26h to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
17m57.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ls792/azure-scheduler-sm26h in 3m18.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-sm26h.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 2 nodes to become ready in 10m18.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-ls792/azure-scheduler-sm26h to rollout in 3m57.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-ls792/azure-scheduler-sm26h to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ls792/azure-scheduler-sm26h 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-6b87678b9b-dk9g6 has a restartCount > 0 (5)
TestCreateCluster
29m44.78s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-dlbqp/create-cluster-28bnt in 2m30s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-28bnt util.go:2949: Successfully waited for HostedCluster e2e-clusters-dlbqp/create-cluster-28bnt to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
17m7.56s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dlbqp/create-cluster-28bnt in 3m18.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-create-cluster-28bnt.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 30.9s util.go:565: Successfully waited for 2 nodes to become ready in 10m12.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-dlbqp/create-cluster-28bnt to rollout in 3m0.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-dlbqp/create-cluster-28bnt to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-dlbqp/create-cluster-28bnt 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-85548c9d95-x2xlz has a restartCount > 0 (6)
TestCreateClusterCustomConfig
33m49.91s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m5kck/custom-config-b6d2t in 2m13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-b6d2t util.go:2949: Successfully waited for HostedCluster e2e-clusters-m5kck/custom-config-b6d2t to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
21m40.5s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m5kck/custom-config-b6d2t in 2m51.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-b6d2t.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-custom-config-b6d2t.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-custom-config-b6d2t.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 45.4s util.go:565: Successfully waited for 2 nodes to become ready in 10m9.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-m5kck/custom-config-b6d2t to rollout in 7m48.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-m5kck/custom-config-b6d2t to have valid conditions in 50ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
190ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m5kck/custom-config-b6d2t 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-77bb797895-hdmkc has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
26m26s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-vs5jn/node-pool-kkxr5 in 2m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-kkxr5 util.go:2949: Successfully waited for HostedCluster e2e-clusters-vs5jn/node-pool-kkxr5 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
13m4.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vs5jn/node-pool-kkxr5 in 3m6.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-kkxr5.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-kkxr5.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 18.375s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-vs5jn/node-pool-kkxr5 to have valid conditions in 9m33.1s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
230ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-vs5jn/node-pool-kkxr5 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-6fb6db7b7d-md4l2 has a restartCount > 0 (2)
TestNodePool/HostedCluster2
25m42.46s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-d7tmk/node-pool-7m8lw in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-7m8lw util.go:2949: Successfully waited for HostedCluster e2e-clusters-d7tmk/node-pool-7m8lw to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
12m45.41s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d7tmk/node-pool-7m8lw in 2m39.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-7m8lw.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-7m8lw.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 29.45s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-d7tmk/node-pool-7m8lw to have valid conditions in 9m30.1s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
230ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-d7tmk/node-pool-7m8lw 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-5b8774fd4c-22xhl has a restartCount > 0 (1)
TestUpgradeControlPlane
1h5m48.91s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-v0nmqb5g/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-v0nmqb5g/release@sha256:7be0b01440d1843fdb9111b9e004de27fda819823a4732b86f3366a1a9e266fe hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-q9lv9/control-plane-upgrade-cptvw in 2m16s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-cptvw util.go:2949: Successfully waited for HostedCluster e2e-clusters-q9lv9/control-plane-upgrade-cptvw to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m2.25s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-q9lv9/control-plane-upgrade-cptvw 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 25ms control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-v0nmqb5g/release@sha256:7be0b01440d1843fdb9111b9e004de27fda819823a4732b86f3366a1a9e266fe util.go:598: Successfully waited for HostedCluster e2e-clusters-q9lv9/control-plane-upgrade-cptvw to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-q9lv9/control-plane-upgrade-cptvw 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-9f6494b59-gp9d4 has a restartCount > 0 (9)
TestUpgradeControlPlane/Main/Wait_for_control_plane_components_to_complete_rollout
30m0s
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-q9lv9-control-plane-upgrade-cptvw/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-q9lv9-control-plane-upgrade-cptvw/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)