Created
November 9, 2022 10:42
-
-
Save aojea/cd5bdd6052b509280e0996962bfbd4a9 to your computer and use it in GitHub Desktop.
loadbalancer test output
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| _output/local/bin/linux/amd64/e2e.test --ginkgo.focus="should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service" --context gke_aojea-gke-dev_us-central1-c_cluster-2 --kubeconfig $PWD/kconfig --provider gke --gce-zone us-central1 | |
| Nov 9 10:38:18.592: INFO: Fetching cloud provider for "gke" | |
| I1109 10:38:18.593029 1207706 gce.go:928] Using DefaultTokenSource &oauth2.reuseTokenSource{new:(*oauth2.tokenRefresher)(0xc000a94c00), mu:sync.Mutex{state:0, sema:0x0}, t:(*oauth2.Token)(0xc00098d500)} | |
| W1109 10:38:18.662520 1207706 gce.go:483] No network name or URL specified. | |
| I1109 10:38:18.662698 1207706 e2e.go:125] Starting e2e run "01bf689f-eecf-431c-b464-2e56764338bf" on Ginkgo node 1 | |
| Nov 9 10:38:18.672: INFO: Enabling in-tree volume drivers | |
| Running Suite: Kubernetes e2e suite - /usr/local/google/home/aojea/src/kubernetes | |
| ================================================================================= | |
| Random Seed: 1667990298 - will randomize all specs | |
| Will run 2 of 6611 specs | |
| ------------------------------ | |
| [SynchronizedBeforeSuite] | |
| test/e2e/e2e.go:76 | |
| [SynchronizedBeforeSuite] TOP-LEVEL | |
| test/e2e/e2e.go:76 | |
| Nov 9 10:38:19.357: INFO: lookupDiskImageSources: gcloud error with [[]string{"instance-groups", "list-instances", "", "--format=get(instance)"}]; err:exit status 1 | |
| Nov 9 10:38:19.357: INFO: > ERROR: (gcloud.compute.instance-groups.list-instances) The project property is set to the empty string | |
| Nov 9 10:38:19.357: INFO: > which is invalid. | |
| Nov 9 10:38:19.357: INFO: > To set your project | |
| Nov 9 10:38:19.357: INFO: > run: | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > $ gcloud config set project PROJECT_ID | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > or to unset it | |
| Nov 9 10:38:19.357: INFO: > run: | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > $ gcloud config unset project | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: Cluster image sources lookup failed: exit status 1 | |
| Nov 9 10:38:19.357: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:19.358: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| Nov 9 10:38:19.358: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable | |
| Nov 9 10:38:20.700: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready | |
| Nov 9 10:38:21.141: INFO: 26 / 26 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) | |
| Nov 9 10:38:21.141: INFO: expected 11 pod replicas in namespace 'kube-system', 11 are Running and Ready. | |
| Nov 9 10:38:21.141: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'anetd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'anetd-win' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke-256pd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke-max' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-scaling-10' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-scaling-20' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-windows' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'metadata-proxy-v0.1' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'netd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'nvidia-gpu-device-plugin' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'pdcsi-node' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'pdcsi-node-windows' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: e2e test version: v1.26.0-alpha.3.234+c8ee2f2f799bc2 | |
| Nov 9 10:38:21.416: INFO: kube-apiserver version: v1.22.12-gke.500 | |
| [SynchronizedBeforeSuite] TOP-LEVEL | |
| test/e2e/e2e.go:76 | |
| Nov 9 10:38:21.416: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:21.416: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| Nov 9 10:38:21.543: INFO: Cluster IP family: ipv4 | |
| ------------------------------ | |
| [SynchronizedBeforeSuite] PASSED [2.814 seconds] | |
| [SynchronizedBeforeSuite] | |
| test/e2e/e2e.go:76 | |
| Begin Captured GinkgoWriter Output >> | |
| [SynchronizedBeforeSuite] TOP-LEVEL | |
| test/e2e/e2e.go:76 | |
| Nov 9 10:38:19.357: INFO: lookupDiskImageSources: gcloud error with [[]string{"instance-groups", "list-instances", "", "--format=get(instance)"}]; err:exit status 1 | |
| Nov 9 10:38:19.357: INFO: > ERROR: (gcloud.compute.instance-groups.list-instances) The project property is set to the empty string | |
| Nov 9 10:38:19.357: INFO: > which is invalid. | |
| Nov 9 10:38:19.357: INFO: > To set your project | |
| Nov 9 10:38:19.357: INFO: > run: | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > $ gcloud config set project PROJECT_ID | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > or to unset it | |
| Nov 9 10:38:19.357: INFO: > run: | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: > $ gcloud config unset project | |
| Nov 9 10:38:19.357: INFO: > | |
| Nov 9 10:38:19.357: INFO: Cluster image sources lookup failed: exit status 1 | |
| Nov 9 10:38:19.357: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:19.358: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| Nov 9 10:38:19.358: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable | |
| Nov 9 10:38:20.700: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready | |
| Nov 9 10:38:21.141: INFO: 26 / 26 pods in namespace 'kube-system' are running and ready (0 seconds elapsed) | |
| Nov 9 10:38:21.141: INFO: expected 11 pod replicas in namespace 'kube-system', 11 are Running and Ready. | |
| Nov 9 10:38:21.141: INFO: Waiting up to 5m0s for all daemonsets in namespace 'kube-system' to start | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'anetd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'anetd-win' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke-256pd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'fluentbit-gke-max' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-scaling-10' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-scaling-20' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'gke-metrics-agent-windows' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'kube-proxy' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'metadata-proxy-v0.1' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'netd' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'nvidia-gpu-device-plugin' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 3 / 3 pods ready in namespace 'kube-system' in daemonset 'pdcsi-node' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: 0 / 0 pods ready in namespace 'kube-system' in daemonset 'pdcsi-node-windows' (0 seconds elapsed) | |
| Nov 9 10:38:21.312: INFO: e2e test version: v1.26.0-alpha.3.234+c8ee2f2f799bc2 | |
| Nov 9 10:38:21.416: INFO: kube-apiserver version: v1.22.12-gke.500 | |
| [SynchronizedBeforeSuite] TOP-LEVEL | |
| test/e2e/e2e.go:76 | |
| Nov 9 10:38:21.416: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:21.416: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| Nov 9 10:38:21.543: INFO: Cluster IP family: ipv4 | |
| << End Captured GinkgoWriter Output | |
| ------------------------------ | |
| SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS | |
| ------------------------------ | |
| [sig-network] LoadBalancers | |
| should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes | |
| test/e2e/network/loadbalancer.go:1108 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| set up framework | framework.go:178 | |
| STEP: Creating a kubernetes client 11/09/22 10:38:21.589 | |
| Nov 9 10:38:21.589: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:21.590: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| STEP: Building a namespace api object, basename loadbalancers 11/09/22 10:38:21.59 | |
| STEP: Waiting for a default service account to be provisioned in namespace 11/09/22 10:38:21.998 | |
| STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 11/09/22 10:38:22.206 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:31 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:65 | |
| [It] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes | |
| test/e2e/network/loadbalancer.go:1108 | |
| STEP: creating a UDP service svc-udp with type=LoadBalancer in loadbalancers-3844 11/09/22 10:38:22.825 | |
| STEP: waiting for the UDP service to have a load balancer 11/09/22 10:38:23.661 | |
| Nov 9 10:38:23.661: INFO: Waiting up to 15m0s for service "svc-udp" to have a LoadBalancer | |
| Nov 9 10:38:57.909: INFO: UDP load balancer: 34.133.229.194 | |
| STEP: hitting the UDP service's LoadBalancer with same source port 11/09/22 10:38:57.909 | |
| STEP: creating a backend pod pod-server-1 for the service svc-udp 11/09/22 10:38:57.91 | |
| Nov 9 10:38:58.214: INFO: Waiting up to 5m0s for pod "pod-server-1" in namespace "loadbalancers-3844" to be "running and ready" | |
| Nov 9 10:38:58.363: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 148.808551ms | |
| Nov 9 10:38:58.363: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:38:58.910: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:00.474: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 2.259706129s | |
| Nov 9 10:39:00.474: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:02.473: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 4.258514562s | |
| Nov 9 10:39:02.473: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:02.911: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:04.474: INFO: Pod "pod-server-1": Phase="Running", Reason="", readiness=true. Elapsed: 6.259640925s | |
| Nov 9 10:39:04.474: INFO: The phase of Pod pod-server-1 is Running (Ready = true) | |
| Nov 9 10:39:04.474: INFO: Pod "pod-server-1" satisfied condition "running and ready" | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-3844 to expose endpoints map[pod-server-1:[80]] 11/09/22 10:39:04.579 | |
| Nov 9 10:39:05.061: INFO: successfully validated that service svc-udp in namespace loadbalancers-3844 exposes endpoints map[pod-server-1:[80]] | |
| STEP: checking client pod connected to the backend 1 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:39:05.061 | |
| Nov 9 10:39:06.912: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:10.913: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:14.914: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:18.916: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:22.917: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:26.918: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:30.919: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:31.025: INFO: Connected successfully to hostname: hostname1 | |
| STEP: creating a second backend pod pod-server-2 for the service svc-udp 11/09/22 10:39:31.062 | |
| Nov 9 10:39:31.180: INFO: Waiting up to 5m0s for pod "pod-server-2" in namespace "loadbalancers-3844" to be "running and ready" | |
| Nov 9 10:39:31.320: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 139.385511ms | |
| Nov 9 10:39:31.320: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:32.025: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:32.129: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:39:33.129: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:33.232: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:39:33.430: INFO: Pod "pod-server-2": Phase="Running", Reason="", readiness=true. Elapsed: 2.249502296s | |
| Nov 9 10:39:33.430: INFO: The phase of Pod pod-server-2 is Running (Ready = true) | |
| Nov 9 10:39:33.430: INFO: Pod "pod-server-2" satisfied condition "running and ready" | |
| Nov 9 10:39:33.535: INFO: Cleaning up pod-server-1 pod | |
| Nov 9 10:39:33.694: INFO: Waiting for pod pod-server-1 to disappear | |
| Nov 9 10:39:33.826: INFO: Pod pod-server-1 no longer exists | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-3844 to expose endpoints map[pod-server-2:[80]] 11/09/22 10:39:33.826 | |
| Nov 9 10:39:34.233: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:35.560: INFO: successfully validated that service svc-udp in namespace loadbalancers-3844 exposes endpoints map[pod-server-2:[80]] | |
| STEP: checking client pod connected to the backend 2 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:39:35.56 | |
| Nov 9 10:39:38.234: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:38.338: INFO: Connected successfully to hostname: hostname2 | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/framework/node/init/init.go:32 | |
| Nov 9 10:39:38.561: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:71 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:33 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| dump namespaces | framework.go:196 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| tear down framework | framework.go:193 | |
| STEP: Destroying namespace "loadbalancers-3844" for this suite. 11/09/22 10:39:38.685 | |
| ------------------------------ | |
| • [SLOW TEST] [77.228 seconds] | |
| [sig-network] LoadBalancers | |
| test/e2e/network/common/framework.go:23 | |
| should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes | |
| test/e2e/network/loadbalancer.go:1108 | |
| Begin Captured GinkgoWriter Output >> | |
| [BeforeEach] [sig-network] LoadBalancers | |
| set up framework | framework.go:178 | |
| STEP: Creating a kubernetes client 11/09/22 10:38:21.589 | |
| Nov 9 10:38:21.589: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:38:21.590: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| STEP: Building a namespace api object, basename loadbalancers 11/09/22 10:38:21.59 | |
| STEP: Waiting for a default service account to be provisioned in namespace 11/09/22 10:38:21.998 | |
| STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 11/09/22 10:38:22.206 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:31 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:65 | |
| [It] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes | |
| test/e2e/network/loadbalancer.go:1108 | |
| STEP: creating a UDP service svc-udp with type=LoadBalancer in loadbalancers-3844 11/09/22 10:38:22.825 | |
| STEP: waiting for the UDP service to have a load balancer 11/09/22 10:38:23.661 | |
| Nov 9 10:38:23.661: INFO: Waiting up to 15m0s for service "svc-udp" to have a LoadBalancer | |
| Nov 9 10:38:57.909: INFO: UDP load balancer: 34.133.229.194 | |
| STEP: hitting the UDP service's LoadBalancer with same source port 11/09/22 10:38:57.909 | |
| STEP: creating a backend pod pod-server-1 for the service svc-udp 11/09/22 10:38:57.91 | |
| Nov 9 10:38:58.214: INFO: Waiting up to 5m0s for pod "pod-server-1" in namespace "loadbalancers-3844" to be "running and ready" | |
| Nov 9 10:38:58.363: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 148.808551ms | |
| Nov 9 10:38:58.363: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:38:58.910: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:00.474: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 2.259706129s | |
| Nov 9 10:39:00.474: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:02.473: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 4.258514562s | |
| Nov 9 10:39:02.473: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:02.911: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:04.474: INFO: Pod "pod-server-1": Phase="Running", Reason="", readiness=true. Elapsed: 6.259640925s | |
| Nov 9 10:39:04.474: INFO: The phase of Pod pod-server-1 is Running (Ready = true) | |
| Nov 9 10:39:04.474: INFO: Pod "pod-server-1" satisfied condition "running and ready" | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-3844 to expose endpoints map[pod-server-1:[80]] 11/09/22 10:39:04.579 | |
| Nov 9 10:39:05.061: INFO: successfully validated that service svc-udp in namespace loadbalancers-3844 exposes endpoints map[pod-server-1:[80]] | |
| STEP: checking client pod connected to the backend 1 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:39:05.061 | |
| Nov 9 10:39:06.912: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:10.913: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:14.914: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:18.916: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:22.917: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:26.918: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:30.919: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:31.025: INFO: Connected successfully to hostname: hostname1 | |
| STEP: creating a second backend pod pod-server-2 for the service svc-udp 11/09/22 10:39:31.062 | |
| Nov 9 10:39:31.180: INFO: Waiting up to 5m0s for pod "pod-server-2" in namespace "loadbalancers-3844" to be "running and ready" | |
| Nov 9 10:39:31.320: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 139.385511ms | |
| Nov 9 10:39:31.320: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:39:32.025: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:32.129: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:39:33.129: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:33.232: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:39:33.430: INFO: Pod "pod-server-2": Phase="Running", Reason="", readiness=true. Elapsed: 2.249502296s | |
| Nov 9 10:39:33.430: INFO: The phase of Pod pod-server-2 is Running (Ready = true) | |
| Nov 9 10:39:33.430: INFO: Pod "pod-server-2" satisfied condition "running and ready" | |
| Nov 9 10:39:33.535: INFO: Cleaning up pod-server-1 pod | |
| Nov 9 10:39:33.694: INFO: Waiting for pod pod-server-1 to disappear | |
| Nov 9 10:39:33.826: INFO: Pod pod-server-1 no longer exists | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-3844 to expose endpoints map[pod-server-2:[80]] 11/09/22 10:39:33.826 | |
| Nov 9 10:39:34.233: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:35.560: INFO: successfully validated that service svc-udp in namespace loadbalancers-3844 exposes endpoints map[pod-server-2:[80]] | |
| STEP: checking client pod connected to the backend 2 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:39:35.56 | |
| Nov 9 10:39:38.234: INFO: Connected successfully to: 34.133.229.194:80 | |
| Nov 9 10:39:38.338: INFO: Connected successfully to hostname: hostname2 | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/framework/node/init/init.go:32 | |
| Nov 9 10:39:38.561: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:71 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:33 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| dump namespaces | framework.go:196 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| tear down framework | framework.go:193 | |
| STEP: Destroying namespace "loadbalancers-3844" for this suite. 11/09/22 10:39:38.685 | |
| << End Captured GinkgoWriter Output | |
| ------------------------------ | |
| SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS | |
| ------------------------------ | |
| [sig-network] LoadBalancers | |
| should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes | |
| test/e2e/network/loadbalancer.go:976 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| set up framework | framework.go:178 | |
| STEP: Creating a kubernetes client 11/09/22 10:39:38.853 | |
| Nov 9 10:39:38.853: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:39:38.853: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| STEP: Building a namespace api object, basename loadbalancers 11/09/22 10:39:38.854 | |
| STEP: Waiting for a default service account to be provisioned in namespace 11/09/22 10:39:39.226 | |
| Nov 9 10:39:39.339: INFO: Connected successfully to: 34.133.229.194:80 | |
| STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 11/09/22 10:39:39.436 | |
| Nov 9 10:39:39.442: INFO: Connected successfully to hostname: hostname2 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:31 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:65 | |
| [It] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes | |
| test/e2e/network/loadbalancer.go:976 | |
| STEP: creating a UDP service svc-udp with type=LoadBalancer in loadbalancers-6201 11/09/22 10:39:40.055 | |
| STEP: waiting for the UDP service to have a load balancer 11/09/22 10:39:40.2 | |
| Nov 9 10:39:40.201: INFO: Waiting up to 15m0s for service "svc-udp" to have a LoadBalancer | |
| Nov 9 10:40:08.444: INFO: UDP load balancer: 34.27.6.234 | |
| STEP: hitting the UDP service's LoadBalancer with same source port 11/09/22 10:40:08.444 | |
| STEP: creating a backend pod pod-server-1 for the service svc-udp 11/09/22 10:40:08.444 | |
| Nov 9 10:40:08.592: INFO: Waiting up to 5m0s for pod "pod-server-1" in namespace "loadbalancers-6201" to be "running and ready" | |
| Nov 9 10:40:08.726: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 134.192033ms | |
| Nov 9 10:40:08.726: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:09.445: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:10.836: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 2.243927575s | |
| Nov 9 10:40:10.836: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:12.838: INFO: Pod "pod-server-1": Phase="Running", Reason="", readiness=true. Elapsed: 4.246206674s | |
| Nov 9 10:40:12.838: INFO: The phase of Pod pod-server-1 is Running (Ready = true) | |
| Nov 9 10:40:12.838: INFO: Pod "pod-server-1" satisfied condition "running and ready" | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-6201 to expose endpoints map[pod-server-1:[80]] 11/09/22 10:40:12.944 | |
| Nov 9 10:40:13.428: INFO: successfully validated that service svc-udp in namespace loadbalancers-6201 exposes endpoints map[pod-server-1:[80]] | |
| STEP: checking client pod connected to the backend 1 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:40:13.428 | |
| Nov 9 10:40:13.447: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:17.447: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:21.448: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:25.450: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:29.451: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:33.452: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:37.453: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:41.454: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:45.455: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:45.561: INFO: Connected successfully to hostname: hostname1 | |
| STEP: creating a second backend pod pod-server-2 for the service svc-udp 11/09/22 10:40:46.429 | |
| Nov 9 10:40:46.561: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:46.611: INFO: Waiting up to 5m0s for pod "pod-server-2" in namespace "loadbalancers-6201" to be "running and ready" | |
| Nov 9 10:40:46.664: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:46.749: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 138.244882ms | |
| Nov 9 10:40:46.749: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:47.664: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:47.767: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:48.768: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:48.859: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.248082442s | |
| Nov 9 10:40:48.859: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:48.874: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:49.874: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:49.976: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:50.861: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.250149959s | |
| Nov 9 10:40:50.861: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:50.977: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:51.079: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:52.080: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:52.183: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:52.858: INFO: Pod "pod-server-2": Phase="Running", Reason="", readiness=true. Elapsed: 6.247112007s | |
| Nov 9 10:40:52.858: INFO: The phase of Pod pod-server-2 is Running (Ready = true) | |
| Nov 9 10:40:52.858: INFO: Pod "pod-server-2" satisfied condition "running and ready" | |
| Nov 9 10:40:52.963: INFO: Cleaning up pod-server-1 pod | |
| Nov 9 10:40:53.117: INFO: Waiting for pod pod-server-1 to disappear | |
| Nov 9 10:40:53.183: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:53.254: INFO: Pod pod-server-1 no longer exists | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-6201 to expose endpoints map[pod-server-2:[80]] 11/09/22 10:40:53.254 | |
| Nov 9 10:40:53.285: INFO: Connected successfully to hostname: hostname2 | |
| Nov 9 10:40:53.724: INFO: successfully validated that service svc-udp in namespace loadbalancers-6201 exposes endpoints map[pod-server-2:[80]] | |
| STEP: checking client pod connected to the backend 2 on Node gke-cluster-2-default-pool-c4846b81-jzk7 11/09/22 10:40:53.724 | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/framework/node/init/init.go:32 | |
| Nov 9 10:40:53.725: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:71 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:33 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| dump namespaces | framework.go:196 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| tear down framework | framework.go:193 | |
| STEP: Destroying namespace "loadbalancers-6201" for this suite. 11/09/22 10:40:53.869 | |
| ------------------------------ | |
| • [SLOW TEST] [75.146 seconds] | |
| [sig-network] LoadBalancers | |
| test/e2e/network/common/framework.go:23 | |
| should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes | |
| test/e2e/network/loadbalancer.go:976 | |
| Begin Captured GinkgoWriter Output >> | |
| [BeforeEach] [sig-network] LoadBalancers | |
| set up framework | framework.go:178 | |
| STEP: Creating a kubernetes client 11/09/22 10:39:38.853 | |
| Nov 9 10:39:38.853: INFO: >>> kubeConfig: /usr/local/google/home/aojea/src/kubernetes/kconfig | |
| Nov 9 10:39:38.853: INFO: >>> kubeContext: gke_aojea-gke-dev_us-central1-c_cluster-2 | |
| STEP: Building a namespace api object, basename loadbalancers 11/09/22 10:39:38.854 | |
| STEP: Waiting for a default service account to be provisioned in namespace 11/09/22 10:39:39.226 | |
| Nov 9 10:39:39.339: INFO: Connected successfully to: 34.133.229.194:80 | |
| STEP: Waiting for kube-root-ca.crt to be provisioned in namespace 11/09/22 10:39:39.436 | |
| Nov 9 10:39:39.442: INFO: Connected successfully to hostname: hostname2 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:31 | |
| [BeforeEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:65 | |
| [It] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes | |
| test/e2e/network/loadbalancer.go:976 | |
| STEP: creating a UDP service svc-udp with type=LoadBalancer in loadbalancers-6201 11/09/22 10:39:40.055 | |
| STEP: waiting for the UDP service to have a load balancer 11/09/22 10:39:40.2 | |
| Nov 9 10:39:40.201: INFO: Waiting up to 15m0s for service "svc-udp" to have a LoadBalancer | |
| Nov 9 10:40:08.444: INFO: UDP load balancer: 34.27.6.234 | |
| STEP: hitting the UDP service's LoadBalancer with same source port 11/09/22 10:40:08.444 | |
| STEP: creating a backend pod pod-server-1 for the service svc-udp 11/09/22 10:40:08.444 | |
| Nov 9 10:40:08.592: INFO: Waiting up to 5m0s for pod "pod-server-1" in namespace "loadbalancers-6201" to be "running and ready" | |
| Nov 9 10:40:08.726: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 134.192033ms | |
| Nov 9 10:40:08.726: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:09.445: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:10.836: INFO: Pod "pod-server-1": Phase="Pending", Reason="", readiness=false. Elapsed: 2.243927575s | |
| Nov 9 10:40:10.836: INFO: The phase of Pod pod-server-1 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:12.838: INFO: Pod "pod-server-1": Phase="Running", Reason="", readiness=true. Elapsed: 4.246206674s | |
| Nov 9 10:40:12.838: INFO: The phase of Pod pod-server-1 is Running (Ready = true) | |
| Nov 9 10:40:12.838: INFO: Pod "pod-server-1" satisfied condition "running and ready" | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-6201 to expose endpoints map[pod-server-1:[80]] 11/09/22 10:40:12.944 | |
| Nov 9 10:40:13.428: INFO: successfully validated that service svc-udp in namespace loadbalancers-6201 exposes endpoints map[pod-server-1:[80]] | |
| STEP: checking client pod connected to the backend 1 on Node gke-cluster-2-default-pool-c4846b81-f5c7 11/09/22 10:40:13.428 | |
| Nov 9 10:40:13.447: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:17.447: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:21.448: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:25.450: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:29.451: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:33.452: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:37.453: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:41.454: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:45.455: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:45.561: INFO: Connected successfully to hostname: hostname1 | |
| STEP: creating a second backend pod pod-server-2 for the service svc-udp 11/09/22 10:40:46.429 | |
| Nov 9 10:40:46.561: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:46.611: INFO: Waiting up to 5m0s for pod "pod-server-2" in namespace "loadbalancers-6201" to be "running and ready" | |
| Nov 9 10:40:46.664: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:46.749: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 138.244882ms | |
| Nov 9 10:40:46.749: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:47.664: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:47.767: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:48.768: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:48.859: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 2.248082442s | |
| Nov 9 10:40:48.859: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:48.874: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:49.874: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:49.976: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:50.861: INFO: Pod "pod-server-2": Phase="Pending", Reason="", readiness=false. Elapsed: 4.250149959s | |
| Nov 9 10:40:50.861: INFO: The phase of Pod pod-server-2 is Pending, waiting for it to be Running (with Ready = true) | |
| Nov 9 10:40:50.977: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:51.079: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:52.080: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:52.183: INFO: Connected successfully to hostname: hostname1 | |
| Nov 9 10:40:52.858: INFO: Pod "pod-server-2": Phase="Running", Reason="", readiness=true. Elapsed: 6.247112007s | |
| Nov 9 10:40:52.858: INFO: The phase of Pod pod-server-2 is Running (Ready = true) | |
| Nov 9 10:40:52.858: INFO: Pod "pod-server-2" satisfied condition "running and ready" | |
| Nov 9 10:40:52.963: INFO: Cleaning up pod-server-1 pod | |
| Nov 9 10:40:53.117: INFO: Waiting for pod pod-server-1 to disappear | |
| Nov 9 10:40:53.183: INFO: Connected successfully to: 34.27.6.234:80 | |
| Nov 9 10:40:53.254: INFO: Pod pod-server-1 no longer exists | |
| STEP: waiting up to 3m0s for service svc-udp in namespace loadbalancers-6201 to expose endpoints map[pod-server-2:[80]] 11/09/22 10:40:53.254 | |
| Nov 9 10:40:53.285: INFO: Connected successfully to hostname: hostname2 | |
| Nov 9 10:40:53.724: INFO: successfully validated that service svc-udp in namespace loadbalancers-6201 exposes endpoints map[pod-server-2:[80]] | |
| STEP: checking client pod connected to the backend 2 on Node gke-cluster-2-default-pool-c4846b81-jzk7 11/09/22 10:40:53.724 | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/framework/node/init/init.go:32 | |
| Nov 9 10:40:53.725: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready | |
| [AfterEach] [sig-network] LoadBalancers | |
| test/e2e/network/loadbalancer.go:71 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| test/e2e/framework/metrics/init/init.go:33 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| dump namespaces | framework.go:196 | |
| [DeferCleanup (Each)] [sig-network] LoadBalancers | |
| tear down framework | framework.go:193 | |
| STEP: Destroying namespace "loadbalancers-6201" for this suite. 11/09/22 10:40:53.869 | |
| << End Captured GinkgoWriter Output | |
| ------------------------------ | |
| SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS | |
| ------------------------------ | |
| [SynchronizedAfterSuite] | |
| test/e2e/e2e.go:87 | |
| [SynchronizedAfterSuite] TOP-LEVEL | |
| test/e2e/e2e.go:87 | |
| [SynchronizedAfterSuite] TOP-LEVEL | |
| test/e2e/e2e.go:87 | |
| Nov 9 10:40:54.096: INFO: Running AfterSuite actions on node 1 | |
| ------------------------------ | |
| [SynchronizedAfterSuite] PASSED [0.000 seconds] | |
| [SynchronizedAfterSuite] | |
| test/e2e/e2e.go:87 | |
| Begin Captured GinkgoWriter Output >> | |
| [SynchronizedAfterSuite] TOP-LEVEL | |
| test/e2e/e2e.go:87 | |
| [SynchronizedAfterSuite] TOP-LEVEL | |
| test/e2e/e2e.go:87 | |
| Nov 9 10:40:54.096: INFO: Running AfterSuite actions on node 1 | |
| << End Captured GinkgoWriter Output | |
| ------------------------------ | |
| [ReportAfterSuite] Kubernetes e2e suite report | |
| test/e2e/e2e_test.go:152 | |
| [ReportAfterSuite] TOP-LEVEL | |
| test/e2e/e2e_test.go:152 | |
| ------------------------------ | |
| [ReportAfterSuite] PASSED [0.000 seconds] | |
| [ReportAfterSuite] Kubernetes e2e suite report | |
| test/e2e/e2e_test.go:152 | |
| Begin Captured GinkgoWriter Output >> | |
| [ReportAfterSuite] TOP-LEVEL | |
| test/e2e/e2e_test.go:152 | |
| << End Captured GinkgoWriter Output | |
| ------------------------------ | |
| Ran 2 of 6611 Specs in 155.367 seconds | |
| SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 6609 Skipped | |
| PASS |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment