PR #7404 - 01-09 13:17

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
32m4.74s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-cj8xs/autoscaling-z2th9 in 2m44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-z2th9 util.go:2949: Successfully waited for HostedCluster e2e-clusters-cj8xs/autoscaling-z2th9 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
17m58.2s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cj8xs/autoscaling-z2th9 in 2m45.05s util.go:301: Successfully waited for kubeconfig secret to have data in 75ms eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-z2th9.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 24.275s util.go:565: Successfully waited for 1 nodes to become ready in 10m18.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-cj8xs/autoscaling-z2th9 to rollout in 4m24.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-cj8xs/autoscaling-z2th9 to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
190ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-cj8xs/autoscaling-z2th9 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-5ffc87db97-wxn9x has a restartCount > 0 (6)
TestAzureScheduler
31m55.69s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-ds8mw/azure-scheduler-h8gvr in 2m29s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-h8gvr util.go:2949: Successfully waited for HostedCluster e2e-clusters-ds8mw/azure-scheduler-h8gvr to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
17m57.8s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ds8mw/azure-scheduler-h8gvr 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-azure-scheduler-h8gvr.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-h8gvr.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 35.575s util.go:565: Successfully waited for 2 nodes to become ready in 11m30.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-ds8mw/azure-scheduler-h8gvr to rollout in 2m54.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-ds8mw/azure-scheduler-h8gvr to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
260ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ds8mw/azure-scheduler-h8gvr 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-59b8f57874-x8pj2 has a restartCount > 0 (6)
TestCreateCluster
30m48.41s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-rdbq8/create-cluster-92p97 in 2m27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-92p97 util.go:2949: Successfully waited for HostedCluster e2e-clusters-rdbq8/create-cluster-92p97 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
17m47.21s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rdbq8/create-cluster-92p97 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-create-cluster-92p97.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.4s util.go:565: Successfully waited for 2 nodes to become ready in 10m24.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-rdbq8/create-cluster-92p97 to rollout in 3m48.075s util.go:2949: Successfully waited for HostedCluster e2e-clusters-rdbq8/create-cluster-92p97 to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
180ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-rdbq8/create-cluster-92p97 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-65f94dc5c6-sp8hm has a restartCount > 0 (6)
TestCreateClusterCustomConfig
34m34.87s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-27p9z/custom-config-wk98c in 2m12s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-wk98c util.go:2949: Successfully waited for HostedCluster e2e-clusters-27p9z/custom-config-wk98c to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
21m59.56s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-27p9z/custom-config-wk98c in 3m3.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-wk98c.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.35s util.go:565: Successfully waited for 2 nodes to become ready in 10m30.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-27p9z/custom-config-wk98c to rollout in 7m36.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-27p9z/custom-config-wk98c to have valid conditions in 50ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
300ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-27p9z/custom-config-wk98c 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-67f6f8b79c-qc4vh has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
26m14.26s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bpt8r/node-pool-n8cgd in 2m31s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-n8cgd util.go:2949: Successfully waited for HostedCluster e2e-clusters-bpt8r/node-pool-n8cgd to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
13m6.86s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bpt8r/node-pool-n8cgd in 2m57.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-n8cgd.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-n8cgd.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 15.25s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-bpt8r/node-pool-n8cgd to have valid conditions in 9m48.075s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bpt8r/node-pool-n8cgd 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-7789884f8c-hjfc8 has a restartCount > 0 (4)
TestNodePool/HostedCluster2
26m13.32s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qhglt/node-pool-jclw8 in 2m18s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-jclw8 util.go:2949: Successfully waited for HostedCluster e2e-clusters-qhglt/node-pool-jclw8 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
13m16.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qhglt/node-pool-jclw8 in 3m3.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-jclw8.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 33.3s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-qhglt/node-pool-jclw8 to have valid conditions in 9m33.075s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
270ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qhglt/node-pool-jclw8 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-77c9685476-qnh65 has a restartCount > 0 (4)
TestUpgradeControlPlane
1h6m11.37s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-knv7dmtw/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-knv7dmtw/release@sha256:e38dc0a11ee9cb116d71a991fdfba27d8cb2fe78560f5875cbaa1cf1ee3717e9 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-mgncd/control-plane-upgrade-5m542 in 2m37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-5m542 util.go:2949: Successfully waited for HostedCluster e2e-clusters-mgncd/control-plane-upgrade-5m542 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m1.67s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mgncd/control-plane-upgrade-5m542 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-knv7dmtw/release@sha256:e38dc0a11ee9cb116d71a991fdfba27d8cb2fe78560f5875cbaa1cf1ee3717e9 util.go:598: Successfully waited for HostedCluster e2e-clusters-mgncd/control-plane-upgrade-5m542 to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
220ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-mgncd/control-plane-upgrade-5m542 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-5469c5fd96-qrbpf 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-mgncd-control-plane-upgrade-5m542/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-mgncd-control-plane-upgrade-5m542/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)