[kubernetes/kubernetes] Flaky: Kubectl expose should create services for rc on gce (#45705)

1 view
Skip to first unread message

Erick Fejta

unread,
May 12, 2017, 3:16:32 AM5/12/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

Flaked 6 times this week in the blocking pull-kubernetes-e2e-gce-etce3 suite.

6 failure clusters: https://storage.googleapis.com/k8s-gubernator/triage/index.html?ci=0&pr=1&test=Kubectl%20expose%20should%20create%20services%20for%20rc

I suspect the most likely source of flakiness is the namespace deletion timeout cluster:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:127
May 10 19:55:13.652: Couldn't delete ns: "e2e-tests-kubectl-00plg": namespace e2e-tests-kubectl-00plg was not deleted with limit: timed out waiting for the condition, namespaced content other than pods remain (&errors.errorString{s:"namespace e2e-tests-kubectl-00plg was not deleted with limit: timed out waiting for the condition, namespaced content other than pods remain"})
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:279

@kubernetes/sig-api-machinery-test-failures
/kind flake

Assigning to sig-api-machinery per namespace timeout:
/assign @lavalamp @deads2k
Please /assign someone to investigate and /unassign yourself.
If there is a more appropriate sig please /sig-remove api-machinery and /sig better-sig


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Erick Fejta

unread,
May 12, 2017, 3:31:19 AM5/12/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

/priority important-soon

Jago Macleod

unread,
May 17, 2017, 3:54:42 PM5/17/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

/unassign @deads2k @lavalamp (whom expect are full-on, heads-down on other things)
/assign @cheftako who has slightly better chances.
Leaving @derekwaynecarr.

Clayton Coleman

unread,
May 17, 2017, 4:47:13 PM5/17/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

Adding debug info into #42975 to get more signal.

Jago Macleod

unread,
May 19, 2017, 1:27:01 PM5/19/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

/unassign @deads2k @lavalamp
/assign @cheftako
Hm. Didn't work. Trying again.

Jago Macleod

unread,
May 19, 2017, 1:27:15 PM5/19/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

/unassign @deads2k

Kubernetes Submit Queue

unread,
Jun 21, 2017, 6:19:22 PM6/21/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

This Issue hasn't been active in 33 days. It will be closed in 56 days (Aug 17, 2017).

cc @cheftako @derekwaynecarr @fejta

You can add 'keep-open' label to prevent this from happening, or add a comment to keep it open another 90 days

Kubernetes Submit Queue

unread,
Jul 25, 2017, 5:13:15 PM7/25/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

This Issue hasn't been active in 67 days. It will be closed in 22 days (Aug 17, 2017).

cc @cheftako @derekwaynecarr @fejta

You can add 'keep-open' label to prevent this from happening, or add a comment to keep it open another 90 days

Kubernetes Submit Queue

unread,
Aug 18, 2017, 4:07:34 AM8/18/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

This Issue hasn't been active in 90 days. Closing this Issue. Please reopen if you would like to work towards merging this change, if/when the Issue is ready for the next round of review.

cc @cheftako @derekwaynecarr @fejta

You can add 'keep-open' label to prevent this from happening again, or add a comment to keep it open another 90 days

Kubernetes Submit Queue

unread,
Aug 18, 2017, 4:07:37 AM8/18/17
to kubernetes/kubernetes, k8s-mirror-api-machinery-test-failures, Team mention

Closed #45705.

Reply all
Reply to author
Forward
0 new messages