kubernetes: Timeout waiting for the condition during V1Job tests

Triage history cluster: https://storage.googleapis.com/k8s-gubernator/triage/index.html?test=v1job#63a36434077ff31ae29e

Note that the triage history page’s filters at the top allow you to focus on specific jobs or tests

73 different tests across 115 jobs are failing in this pattern.

The apps part of this issue is:

V1Job should fail a job in upgrades from 1.4 - #44602

Previous things:

NFSv3 should be mountable for NFSv3 in gke-staging and gke-prod https://github.com/kubernetes/kubernetes/issues/44695
Services should only allow access from service loadbalancer source ranges in kops-aws-slow https://github.com/kubernetes/kubernetes/issues/44514

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 19 (19 by maintainers)

Commits related to this issue

Merge pull request #44602 from soltysh/issue44410 Automatic merge from submit-queue Speed up job's e2e when waiting for failure This is cherry-pick of #31973 to address job part of the problem from... — committed to kubernetes/kubernetes by deleted user 7 years ago

Most upvoted comments

Yay! Thank you so much!

And if you look there are zero hits of this cluster after 4a today: https://storage.googleapis.com/k8s-gubernator/triage/index.html?test=v1job#63a36434077ff31ae29e

+2

fejta on Apr 27, 2017

https://github.com/kubernetes/kubernetes/pull/44602 merged so I’m closing this.

+2

soltysh on Apr 27, 2017

Read more comments on GitHub

← kubernetes: Timeout expired waiting for volumes to attach

kubernetes: Timeouts when draining a node while using external-traffic: OnlyLocal annotation on loadbalancer →