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

Flaky SchedulerPredicates e2e tests because of undeleted namespaces #77928

Open
OlegLoewen opened this issue May 15, 2019 · 3 comments

Comments

Projects
None yet
3 participants
@OlegLoewen
Copy link

commented May 15, 2019

Which test(s) are failing:

  • [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance]
  • [sig-scheduling] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance]
  • [sig-scheduling] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance]

Details
I'm still facing this issue which causes flakiness:

/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:79
Expected error:
    <*errors.errorString | 0xc0011b21a0>: {
        s: "Namespace e2e-tests-container-probe-5dp7g is active",
    }
    Namespace e2e-tests-container-probe-5dp7g is active
not to have occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:88

system-out output:

go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:147
STEP: Creating a kubernetes client
STEP: Building a namespace api object, basename sched-pred
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in e2e-tests-sched-pred-h67w2
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-scheduling] SchedulerPredicates [Serial]
  /go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:78
May 13 09:30:03.176: INFO: Waiting up to 1m0s for all (but 2) nodes to be ready
May 13 09:30:03.184: INFO: Waiting for terminating namespaces to be deleted...
May 13 09:30:03.186: INFO: Unexpected error occurred: Namespace e2e-tests-gc-5vwws is active
[AfterEach] [sig-scheduling] SchedulerPredicates [Serial]
  /go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:148
STEP: Collecting events from namespace "e2e-tests-sched-pred-h67w2".
STEP: Found 0 events.

I tested this testcases with different cloud providers (gce, aws, alicloud, openstack, azure) and have observed, that this issue is only happening for gce and alicloud clusters and only for k8s release < 1.14.0

@OlegLoewen

This comment has been minimized.

Copy link
Author

commented May 15, 2019

/sig scheduling

@OlegLoewen

This comment has been minimized.

Copy link
Author

commented May 15, 2019

/assign @BenTheElder

@OlegLoewen OlegLoewen changed the title Falky SchedulerPredicates e2e tests because of undeleted namespaces Flaky SchedulerPredicates e2e tests because of undeleted namespaces May 15, 2019

@BenTheElder

This comment has been minimized.

Copy link
Member

commented May 16, 2019

if it's only happening for older releases, perhaps a fix was added?

I do not own scheduling tests.
/unassign
cc @spiffxp for conformance
@kubernetes/sig-scheduling-misc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.