PR #7439 - 01-09 09:13

Job: hypershift
FAILURE
← Back to Test Grid

Test Summary

149
Total Tests
99
Passed
31
Failed
19
Skipped

Failed Tests

TestAutoscaling
21m27.69s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-lqq6s/autoscaling-ck7kz in 55s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster autoscaling-ck7kz util.go:2949: Successfully waited for HostedCluster e2e-clusters-lqq6s/autoscaling-ck7kz to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestAutoscaling/ValidateHostedCluster
14m1.27s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lqq6s/autoscaling-ck7kz in 1m42s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-ck7kz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-autoscaling-ck7kz.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-autoscaling-ck7kz.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.200.246.255:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m26.025s util.go:565: Successfully waited for 1 nodes to become ready in 6m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-lqq6s/autoscaling-ck7kz to rollout in 4m0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-lqq6s/autoscaling-ck7kz to have valid conditions in 0s
TestAutoscaling/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lqq6s/autoscaling-ck7kz in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-8b84df8c7-v72gg has a restartCount > 0 (6)
TestCreateCluster
25m27.74s
create_cluster_test.go:2492: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-lrzwf/create-cluster-64xnr in 37s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster create-cluster-64xnr util.go:2949: Successfully waited for HostedCluster e2e-clusters-lrzwf/create-cluster-64xnr to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateCluster/ValidateHostedCluster
17m52.4s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lrzwf/create-cluster-64xnr in 1m51s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-64xnr.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-create-cluster-64xnr.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-create-cluster-64xnr.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.209.187.20:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m2.1s util.go:565: Successfully waited for 3 nodes to become ready in 8m21s util.go:598: Successfully waited for HostedCluster e2e-clusters-lrzwf/create-cluster-64xnr to rollout in 6m33s util.go:2949: Successfully waited for HostedCluster e2e-clusters-lrzwf/create-cluster-64xnr to have valid conditions in 0s
TestCreateCluster/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-lrzwf/create-cluster-64xnr in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-78b459d8db-kczn4 has a restartCount > 0 (7)
TestCreateClusterCustomConfig
26m29.69s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-kcdlh/custom-config-42bcd in 26s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster custom-config-42bcd util.go:2949: Successfully waited for HostedCluster e2e-clusters-kcdlh/custom-config-42bcd to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterCustomConfig/ValidateHostedCluster
19m59.28s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kcdlh/custom-config-42bcd in 1m9s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-42bcd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-custom-config-42bcd.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-42bcd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 34.201.178.193:443: i/o timeout eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-custom-config-42bcd.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 52.7.203.124:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 2m27.05s util.go:565: Successfully waited for 2 nodes to become ready in 7m51s util.go:598: Successfully waited for HostedCluster e2e-clusters-kcdlh/custom-config-42bcd to rollout in 8m27s util.go:2949: Successfully waited for HostedCluster e2e-clusters-kcdlh/custom-config-42bcd to have valid conditions in 0s
TestCreateClusterCustomConfig/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-kcdlh/custom-config-42bcd in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-7db687b457-ztgql has a restartCount > 0 (7)
TestCreateClusterPrivate
22m44.1s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-zfz9h/private-s997t in 44s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-s997t util.go:2949: Successfully waited for HostedCluster e2e-clusters-zfz9h/private-s997t to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivate/ValidateHostedCluster
15m36.21s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zfz9h/private-s997t in 1m27s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-zfz9h/private-s997t to have all of their desired nodes in 9m48s util.go:598: Successfully waited for HostedCluster e2e-clusters-zfz9h/private-s997t to rollout in 4m21s util.go:2949: Successfully waited for HostedCluster e2e-clusters-zfz9h/private-s997t to have valid conditions in 0s
TestCreateClusterPrivate/ValidateHostedCluster/EnsureNoCrashingPods
60ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-zfz9h/private-s997t in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-55b4b8d477-zm8br has a restartCount > 0 (7)
TestCreateClusterPrivateWithRouteKAS
25m56.85s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-5fjcj/private-ch464 in 40s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster private-ch464 util.go:2949: Successfully waited for HostedCluster e2e-clusters-5fjcj/private-ch464 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster
18m51.14s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5fjcj/private-ch464 in 1m48s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:695: Successfully waited for NodePools for HostedCluster e2e-clusters-5fjcj/private-ch464 to have all of their desired nodes in 10m30s util.go:598: Successfully waited for HostedCluster e2e-clusters-5fjcj/private-ch464 to rollout in 6m3s util.go:2949: Successfully waited for HostedCluster e2e-clusters-5fjcj/private-ch464 to have valid conditions in 0s
TestCreateClusterPrivateWithRouteKAS/ValidateHostedCluster/EnsureNoCrashingPods
30.03s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-5fjcj/private-ch464 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-75fccc5bf7-lzzll has a restartCount > 0 (7)
TestCreateClusterProxy
25m6.73s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-bbt4m/proxy-bprs6 in 28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster proxy-bprs6 util.go:2949: Successfully waited for HostedCluster e2e-clusters-bbt4m/proxy-bprs6 to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterProxy/ValidateHostedCluster
17m35.24s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bbt4m/proxy-bprs6 in 1m39s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-bprs6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-proxy-bprs6.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-proxy-bprs6.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.219.60.138:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m27.025s util.go:565: Successfully waited for 2 nodes to become ready in 8m18s util.go:598: Successfully waited for HostedCluster e2e-clusters-bbt4m/proxy-bprs6 to rollout in 6m6s util.go:2949: Successfully waited for HostedCluster e2e-clusters-bbt4m/proxy-bprs6 to have valid conditions in 0s
TestCreateClusterProxy/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-bbt4m/proxy-bprs6 in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-67c6645d5-wg2d2 has a restartCount > 0 (7)
TestCreateClusterRequestServingIsolation
30m17.3s
requestserving.go:105: Created request serving nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-r77vm requestserving.go:105: Created request serving nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-xr5pv requestserving.go:113: Created non request serving nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-xwkm5 requestserving.go:113: Created non request serving nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-89xhh requestserving.go:113: Created non request serving nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-zh6dv util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-r77vm in 3m51s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-xr5pv in 3s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-xwkm5 in 36s util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-89xhh in 100ms util.go:565: Successfully waited for 1 nodes to become ready for NodePool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-zh6dv in 30s create_cluster_test.go:2670: Sufficient zones available for InfrastructureAvailabilityPolicy HighlyAvailable hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw in 24s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster request-serving-isolation-pmhkw util.go:2949: Successfully waited for HostedCluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() requestserving.go:132: Tearing down custom nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-r77vm requestserving.go:132: Tearing down custom nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-reqserving-xr5pv requestserving.go:132: Tearing down custom nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-xwkm5 requestserving.go:132: Tearing down custom nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-89xhh requestserving.go:132: Tearing down custom nodepool clusters/9ba7a7ad560f6d0d6617-mgmt-non-reqserving-zh6dv hypershift_framework.go:230: skipping teardown, already called
TestCreateClusterRequestServingIsolation/ValidateHostedCluster
17m57.42s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw in 1m24s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-pmhkw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-request-serving-isolation-pmhkw.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-request-serving-isolation-pmhkw.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 3.212.225.85:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m37.1s util.go:565: Successfully waited for 3 nodes to become ready in 8m15s util.go:598: Successfully waited for HostedCluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw to rollout in 6m9s util.go:2949: Successfully waited for HostedCluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw to have valid conditions in 27s
TestCreateClusterRequestServingIsolation/ValidateHostedCluster/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-2wnv4/request-serving-isolation-pmhkw in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-68d8569c85-gbx68 has a restartCount > 0 (7)
TestNodePool
0s
TestNodePool/HostedCluster0
10m5.64s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-hgltb/node-pool-bgn2n in 28s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-bgn2n util.go:2949: Successfully waited for HostedCluster e2e-clusters-hgltb/node-pool-bgn2n to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster0/ValidateHostedCluster
5m40.31s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hgltb/node-pool-bgn2n in 1m18s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bgn2n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-bgn2n.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-bgn2n.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 13.217.73.89:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m47.025s util.go:565: Successfully waited for 0 nodes to become ready in 0s util.go:2949: Successfully waited for HostedCluster e2e-clusters-hgltb/node-pool-bgn2n to have valid conditions in 2m30s
TestNodePool/HostedCluster0/ValidateHostedCluster/EnsureNoCrashingPods
30ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-hgltb/node-pool-bgn2n in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-6564f9d7fc-qh2v8 has a restartCount > 0 (3)
TestNodePool/HostedCluster2
10m24.19s
hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-m5b4l/node-pool-xrx4m in 48s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster node-pool-xrx4m util.go:2949: Successfully waited for HostedCluster e2e-clusters-m5b4l/node-pool-xrx4m to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestNodePool/HostedCluster2/ValidateHostedCluster
5m41.35s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m5b4l/node-pool-xrx4m in 1m39s util.go:301: Successfully waited for kubeconfig secret to have data in 0s eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-xrx4m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp: lookup api-node-pool-xrx4m.service.ci.hypershift.devcluster.openshift.com on 172.30.0.10:53: no such host eventually.go:104: Failed to get *v1.SelfSubjectReview: Post "https://api-node-pool-xrx4m.service.ci.hypershift.devcluster.openshift.com:443/apis/authentication.k8s.io/v1/selfsubjectreviews": dial tcp 35.171.148.196:443: i/o timeout util.go:363: Successfully waited for a successful connection to the guest API server in 1m30.05s util.go:565: Successfully waited for 0 nodes to become ready in 25ms util.go:2949: Successfully waited for HostedCluster e2e-clusters-m5b4l/node-pool-xrx4m to have valid conditions in 2m27s
TestNodePool/HostedCluster2/ValidateHostedCluster/EnsureNoCrashingPods
20ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-m5b4l/node-pool-xrx4m in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-d7695ccb9-h675f has a restartCount > 0 (4)
TestUpgradeControlPlane
52m52.82s
control_plane_upgrade_test.go:25: Starting control plane upgrade test. FromImage: registry.build01.ci.openshift.org/ci-op-90jbjmwh/release@sha256:7265c8d8ccfe02e12221b71fdce3624e4307044c6d689d098552eb5ffc716041, toImage: registry.build01.ci.openshift.org/ci-op-90jbjmwh/release@sha256:2e382f822735f5155daed27abc63f3995c68756ec48c18b9dad5fe4a1d58ba15 hypershift_framework.go:430: Successfully created hostedcluster e2e-clusters-n4kp6/control-plane-upgrade-m64kq in 20s hypershift_framework.go:119: Summarizing unexpected conditions for HostedCluster control-plane-upgrade-m64kq util.go:2949: Successfully waited for HostedCluster e2e-clusters-n4kp6/control-plane-upgrade-m64kq to have valid conditions in 0s hypershift_framework.go:249: skipping postTeardown() hypershift_framework.go:230: skipping teardown, already called
TestUpgradeControlPlane/Main
29m10.56s
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n4kp6/control-plane-upgrade-m64kq in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:363: Successfully waited for a successful connection to the guest API server in 0s control_plane_upgrade_test.go:52: Updating cluster image. Image: registry.build01.ci.openshift.org/ci-op-90jbjmwh/release@sha256:2e382f822735f5155daed27abc63f3995c68756ec48c18b9dad5fe4a1d58ba15 util.go:598: Successfully waited for HostedCluster e2e-clusters-n4kp6/control-plane-upgrade-m64kq to rollout in 0s
TestUpgradeControlPlane/Main/EnsureNoCrashingPods
40ms
util.go:284: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-n4kp6/control-plane-upgrade-m64kq in 0s util.go:301: Successfully waited for kubeconfig secret to have data in 0s util.go:782: Container controller in pod cloud-network-config-controller-5889866c85-54cmj has a restartCount > 0 (8)