PR #7450 - 01-09 13:49

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

112
Total Tests
72
Passed
23
Failed
17
Skipped

Failed Tests

TestAutoscaling
32m12.06s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5nqxw/autoscaling-psp7c in 2m27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-psp7c util.go:2949: Successfully waited for HostedCluster e2e-clusters-5nqxw/autoscaling-psp7c to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
19m40.2s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5nqxw/autoscaling-psp7c 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-autoscaling-psp7c.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 27.35s util.go:565: Successfully waited for 1 nodes to become ready in 10m57.05s util.go:598: Successfully waited for HostedCluster e2e-clusters-5nqxw/autoscaling-psp7c to rollout in 5m6.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-5nqxw/autoscaling-psp7c to have valid conditions in 50ms
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5nqxw/autoscaling-psp7c 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-bd77885bc-6zsl8 has a restartCount > 0 (6)
TestAzureScheduler
30m8.9s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qtls6/azure-scheduler-p9rsk in 2m27s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster azure-scheduler-p9rsk util.go:2949: Successfully waited for HostedCluster e2e-clusters-qtls6/azure-scheduler-p9rsk to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAzureScheduler/ValidateHostedCluster
16m57.16s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qtls6/azure-scheduler-p9rsk in 2m54.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-p9rsk.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.4s util.go:565: Successfully waited for 2 nodes to become ready in 9m48.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-qtls6/azure-scheduler-p9rsk to rollout in 3m51.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-qtls6/azure-scheduler-p9rsk to have valid conditions in 50ms
TestAzureScheduler/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qtls6/azure-scheduler-p9rsk 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-5798d768d4-jvq2b has a restartCount > 0 (5)
TestCreateCluster
29m58.18s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zfhls/create-cluster-8j8nv in 2m15s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-8j8nv util.go:2949: Successfully waited for HostedCluster e2e-clusters-zfhls/create-cluster-8j8nv to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
16m54.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zfhls/create-cluster-8j8nv in 3m15.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-8j8nv.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 11.35s util.go:565: Successfully waited for 2 nodes to become ready in 10m15.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-zfhls/create-cluster-8j8nv to rollout in 3m6.075s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zfhls/create-cluster-8j8nv to have valid conditions in 50ms
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
260ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zfhls/create-cluster-8j8nv in 50ms util.go:301: Successfully waited for kubeconfig secret to have data in 75ms util.go:782: Container controller in pod cloud-network-config-controller-84654474cf-9snt6 has a restartCount > 0 (5)
TestCreateClusterCustomConfig
33m41.08s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-pqmnf/custom-config-xnd4l in 2m17s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-xnd4l util.go:2949: Successfully waited for HostedCluster e2e-clusters-pqmnf/custom-config-xnd4l to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
21m37.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pqmnf/custom-config-xnd4l 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-custom-config-xnd4l.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-xnd4l.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-xnd4l.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 42.625s util.go:565: Successfully waited for 2 nodes to become ready in 10m18.075s util.go:598: Successfully waited for HostedCluster e2e-clusters-pqmnf/custom-config-xnd4l to rollout in 7m33.05s util.go:2949: Successfully waited for HostedCluster e2e-clusters-pqmnf/custom-config-xnd4l to have valid conditions in 50ms
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
210ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-pqmnf/custom-config-xnd4l 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-c4bf648cd-4ch6c has a restartCount > 0 (6)
TestNodePool
0s
TestNodePool/HostedCluster0
25m48.52s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5ztc2/node-pool-wgwqm in 2m44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-wgwqm util.go:2949: Successfully waited for HostedCluster e2e-clusters-5ztc2/node-pool-wgwqm to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
11m54.84s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5ztc2/node-pool-wgwqm 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-wgwqm.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.85s util.go:565: Successfully waited for 0 nodes to become ready in 100ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-5ztc2/node-pool-wgwqm to have valid conditions in 8m12.075s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
290ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5ztc2/node-pool-wgwqm 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-5d964cd6f8-wdswz has a restartCount > 0 (1)
TestNodePool/HostedCluster2
25m20.55s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-652sq/node-pool-q2rcn in 2m24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-q2rcn util.go:2949: Successfully waited for HostedCluster e2e-clusters-652sq/node-pool-q2rcn to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
12m14.85s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-652sq/node-pool-q2rcn 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-q2rcn.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 23.25s util.go:565: Successfully waited for 0 nodes to become ready in 200ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-652sq/node-pool-q2rcn to have valid conditions in 8m42.05s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
220ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-652sq/node-pool-q2rcn 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-8b7b86ddf-frrnb has a restartCount > 0 (1)
TestUpgradeControlPlane
1h0m54.85s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-q9cg5twv/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-q9cg5twv/release@sha256:1d37a56b4370720ea6dc0bdb6f86c60ab314df539f0a0cfd2ba5d156736c8115 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-qjcrh/control-plane-upgrade-g46x2 in 2m14s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-g46x2 util.go:2949: Successfully waited for HostedCluster e2e-clusters-qjcrh/control-plane-upgrade-g46x2 to have valid conditions in 50ms hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
30m1.82s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qjcrh/control-plane-upgrade-g46x2 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-q9cg5twv/release@sha256:1d37a56b4370720ea6dc0bdb6f86c60ab314df539f0a0cfd2ba5d156736c8115 util.go:598: Successfully waited for HostedCluster e2e-clusters-qjcrh/control-plane-upgrade-g46x2 to rollout in 75ms
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
290ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-qjcrh/control-plane-upgrade-g46x2 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-849ff97dbc-mfljl 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-qjcrh-control-plane-upgrade-g46x2/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-qjcrh-control-plane-upgrade-g46x2/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)