PR #7139 - 01-09 14:30

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
28m20.07s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-hrv2n/autoscaling-mjck6 in 2m13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-mjck6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-hrv2n/autoscaling-mjck6 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
15m32.09s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hrv2n/autoscaling-mjck6 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-autoscaling-mjck6.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 22.225s util.go:565: Successfully waited for 1 nodes to become ready in 9m21.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-hrv2n/autoscaling-mjck6 to rollout in 2m45.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-hrv2n/autoscaling-mjck6 to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hrv2n/autoscaling-mjck6 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-786f7fc85b-9kvj7 has a restartCount > 0 (5)
TestAzureScheduler
30m49.8s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-djdjk/azure-scheduler-5gf9n in 2m9s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-5gf9n util.go:2949: Successfully waited for HostedCluster e2e-clusters-djdjk/azure-scheduler-5gf9n to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
17m19.26s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-djdjk/azure-scheduler-5gf9n 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-azure-scheduler-5gf9n.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-5gf9n.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 24.5s util.go:565: Successfully waited for 2 nodes to become ready in 10m21.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-djdjk/azure-scheduler-5gf9n to rollout in 3m39.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-djdjk/azure-scheduler-5gf9n to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-djdjk/azure-scheduler-5gf9n 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-65f88569b6-89fpl has a restartCount > 0 (6)
TestCreateCluster
29m41.3s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-b6wnc/create-cluster-dqnql in 2m13s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-dqnql util.go:2949: Successfully waited for HostedCluster e2e-clusters-b6wnc/create-cluster-dqnql to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
16m31.11s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b6wnc/create-cluster-dqnql 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-create-cluster-dqnql.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 2 nodes to become ready in 9m54.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-b6wnc/create-cluster-dqnql to rollout in 3m21.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-b6wnc/create-cluster-dqnql to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
200ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-b6wnc/create-cluster-dqnql 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-5756484dd8-2dv9d has a restartCount > 0 (5)
TestCreateClusterCustomConfig
33m27.59s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-s2trp/custom-config-5rk29 in 2m34s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-5rk29 util.go:2949: Successfully waited for HostedCluster e2e-clusters-s2trp/custom-config-5rk29 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
20m50.33s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s2trp/custom-config-5rk29 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-5rk29.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 49.525s util.go:565: Successfully waited for 2 nodes to become ready in 9m33.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-s2trp/custom-config-5rk29 to rollout in 7m30.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-s2trp/custom-config-5rk29 to have valid conditions in 50ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s2trp/custom-config-5rk29 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-76b7fd5847-x5t22 has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
24m57.03s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-s6flj/node-pool-j76rv in 2m19s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-j76rv util.go:2949: Successfully waited for HostedCluster e2e-clusters-s6flj/node-pool-j76rv to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
11m49.96s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s6flj/node-pool-j76rv in 3m9.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-j76rv.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 22.275s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-s6flj/node-pool-j76rv to have valid conditions in 8m12.075s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
220ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s6flj/node-pool-j76rv 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-6d6f57575f-kqmxt has a restartCount > 0 (3)
TestNodePool/HostedCluster2
24m36.72s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-s5lbv/node-pool-9kx9v in 2m35s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-9kx9v util.go:2949: Successfully waited for HostedCluster e2e-clusters-s5lbv/node-pool-9kx9v to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
11m33.86s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s5lbv/node-pool-9kx9v in 2m45.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-9kx9v.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-node-pool-9kx9v.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 24.45s util.go:565: Successfully waited for 0 nodes to become ready in 75ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-s5lbv/node-pool-9kx9v to have valid conditions in 8m18.05s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
170ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-s5lbv/node-pool-9kx9v 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-b8485c74b-bzj5m has a restartCount > 0 (3)
TestUpgradeControlPlane
1h1m28.67s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-crcyycm9/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-crcyycm9/release@sha256:554021aa0523789b2b599ff598a5cf9afe7958b3ab0214e826c5a1d4925f10b2 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-9hcn6/control-plane-upgrade-5lc8z in 2m26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-5lc8z util.go:2949: Successfully waited for HostedCluster e2e-clusters-9hcn6/control-plane-upgrade-5lc8z to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m2.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9hcn6/control-plane-upgrade-5lc8z 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-crcyycm9/release@sha256:554021aa0523789b2b599ff598a5cf9afe7958b3ab0214e826c5a1d4925f10b2 util.go:598: Successfully waited for HostedCluster e2e-clusters-9hcn6/control-plane-upgrade-5lc8z to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-9hcn6/control-plane-upgrade-5lc8z 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-5b864bb9d-5ljhr 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-9hcn6-control-plane-upgrade-5lc8z/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-9hcn6-control-plane-upgrade-5lc8z/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)