Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Failing test] Conformance-GCE-master (ci-kubernetes-gce-conformance-latest) #84980

Closed
alenkacz opened this issue Nov 8, 2019 · 5 comments · Fixed by #84988

Comments

@alenkacz
Copy link
Contributor

@alenkacz alenkacz commented Nov 8, 2019

Which jobs are failing:
Conformance-GCE-master

Which test(s) are failing:

[sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]Changes

[sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]Changes

Since when has it been failing:
11-07 14:41 PST probably after this PR got merged 62f66ea

Testgrid link:
https://k8s-testgrid.appspot.com/sig-release-master-blocking#Conformance%20-%20GCE%20-%20master

Reason for failure:

I1108 08:03:43.432] �[90m/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:34�[0m
I1108 08:03:43.433]   �[91m�[1mvalidates that NodeSelector is respected if not matching  [Conformance] [It]�[0m
I1108 08:03:43.433]   �[90m/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:680�[0m
I1108 08:03:43.433] 
I1108 08:03:43.433]   �[91mNov  8 08:03:42.506: Timed out after 10m0s waiting for stable cluster.�[0m
I1108 08:03:43.434] 
I1108 08:03:43.434]   /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/framework.go:55

Anything else we need to know:
/cc @droslean @hasheddan @alejandrox1

/sig scheduling
/milestone v1.17
/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Nov 8, 2019
@alenkacz alenkacz added this to New (no response yet) in 1.17 CI Signal Nov 8, 2019
@alenkacz

This comment has been minimized.

Copy link
Contributor Author

@alenkacz alenkacz commented Nov 8, 2019

/assign draveness ahg-g

@ahg-g

This comment has been minimized.

Copy link
Member

@ahg-g ahg-g commented Nov 8, 2019

it is actually after #84806, which was trying to fix

[sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]Changes

WaitForStableCluster is timing out, sadly there are not enough logs from the test to understand why, but likely because there are pods in a namespace other than kube-system from previous tests that never get deleted.

@alenkacz

This comment has been minimized.

Copy link
Contributor Author

@alenkacz alenkacz commented Nov 8, 2019

@ahg-g oh I see... so you think it's a flake? Or we need one more fix to the WaitForStableCluster?

@ahg-g

This comment has been minimized.

Copy link
Member

@ahg-g ahg-g commented Nov 8, 2019

We need to fix WaitForStableCluster again.

/cc @damemi

1.17 CI Signal automation moved this from New (no response yet) to Observing (observe test failure/flake before marking as resolved) Nov 8, 2019
@alenkacz

This comment has been minimized.

Copy link
Contributor Author

@alenkacz alenkacz commented Nov 9, 2019

Thanks @ahg-g for such a quick turnover!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
1.17 CI Signal
  
Observing (observe test failure/flake...
4 participants
You can’t perform that action at this time.