Change:
It looks like the addition of some new e2e tests (by ?) made the test run take a bit longer, and not fit into it's timeout threshold. FYI. root 9001 0.0 0.0 6256 ? Sl 08:48 0:00 /workspace/kubernetes/platforms/linux/amd64/ginkgo -- -- --ginkgo.flakeAttempts=1 --host=https://104.198.234.41 --provider=gce --gce-project=k8s-jkns-e2e-gce-federation --gce-zone=us-central1-f --gke-cluster=jenkins-e2e --kube-master=jenkins-us-central1-f-master --cluster-tag= --repo-root=/workspace/kubernetes/cluster/../cluster/gce/../../cluster/gce/../../cluster/.. --node-instance-group=jenkins-us-central1-f-minion-group --prefix=jenkins-us-central1-f --network=jenkins-e2e --master-os-distro=gci --node-os-distro=debian --num-nodes=3 --minStartupPods=8 --report-dir=/workspace/artifacts --[Feature:Federation] root 9009 0.0 0.1 ? Sl 08:48 0:05  --test.timeout=24h -- --ginkgo.slowSpecThreshold=5. -- --ginkgo.flakeAttempts=1 --host=https://104.198.234.41 --provider=gce --gce-project=k8s-jkns-e2e-gce-federation --gce-zone=us-central1-f --gke-cluster=jenkins-e2e --kube-master=jenkins-us-central1-f-master --cluster-tag= --repo-root=/workspace/kubernetes/cluster/../cluster/gce/../../cluster/gce/../../cluster/.. --node-instance-group=jenkins-us-central1-f-minion-group --prefix=jenkins-us-central1-f --network=jenkins-e2e --master-os-distro=gci --node-os-distro=debian --num-nodes=3 --minStartupPods=8 --report-dir=/workspace/artifacts --[Feature:Federation] ++ docker stop kubernetes-e2e-gce-federation-5358 kubernetes-e2e-gce-federation-5358 rc=124 [[ 124 -eq 124 ]] echo 'Build timed out' Build timed out echo 'Exiting with code: 124' Exiting with code: 124 exit 124 Build step 'Execute shell' marked build as failure
We should probably increase the overall timeout value to accommodate the new tests, in advance of doing a cleanup to make the tests run faster.
I havent any tests yet :)
One way of reducing the time of our e2e tests is to register the clusters in the framework instead of doing it in BeforeEach in each test. Each test runs it in its own namespace, so no need to delete and register clusters again for each test
I analyzed the logs in Most of the tests are failing because of service spec. [0].protocol and spec.sessionAffinity field were optional before. something have changed.
it seems no new tests are since 9 days. and i see the federated_informer throwing quite a lot of error, the one below: Increasing the timeout will not help. There is something wrong with the code, maybe related to API versioning.
[FLAKE-PING] This flaky-test issue would love to have more attention.
I think the time out is due to a combination of our failing tests and Whenever a test fails, e2e framework tries to print the logs of some of our pods. But fetching logs is timing out after a long time (as discussed in ). Fixing the tests to not fail should eliminate the timeout failure :)
Regarding [0].protocol and spec.sessionAffinity fields, I see that we are setting them in our tests: Ref
Currently there are 3 testcases which are failing, One is in Federated Ingress and the other two are in Federation API server authentication. I know the cause for API server authentication test failures. By default anonymous-auth is enabled, so api server will accept the request and there are no authorization plugins configured currently, hence the requests are being served. I will send a fix for these 2 failed test cases

Discussion:
- --tls-private-key-file=/srv/kubernetes/server.key - --admission-control={{.FEDERATION_ADMISSION_CONTROL}} - --token-auth-file=/srv/kubernetes/known-tokens.csv <ins> - --anonymous-auth=false </ins> ports: - containerPort: 443 name: https