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 test] NodeLease when the NodeLease feature is enabled the kubelet should report node status infrequently #75370

Closed
mariantalla opened this Issue Mar 14, 2019 · 6 comments

Comments

@mariantalla
Copy link
Contributor

mariantalla commented Mar 14, 2019

Which jobs are failing:

Which test(s) are failing:
NodeLease when the NodeLease feature is enabled the kubelet should report node status infrequently

Since when has it been failing:

Testgrid link:

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node_lease.go:83
Timed out after 300.000s.
Expected
    <*errors.errorString | 0xc00177a260>: {
        s: "node status heartbeat is unchanged for 14.708854559s, waiting for 1m20s",
    }
to be nil
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/node_lease.go:134

Anything else we need to know:

  • #75205 cleared out flakiness in the same place (different error though)

/sig node
/remove-kind failing-test
/kind flake
/sig node
/milestone v1.14
/priority important-soon

cc @liggitt as you worked on #75205 and might have input
cc @smourapina @alejandrox1 @kacole2 @mortent

@mariantalla

This comment has been minimized.

Copy link
Contributor Author

mariantalla commented Mar 14, 2019

This test is currently flaking up to 5% of the time in these jobs.That's not terrible, but the jobs are among the flakiest, so stabilizing it would really help.

@liggitt

This comment has been minimized.

Copy link
Member

liggitt commented Mar 14, 2019

deflake in #75374

@liggitt liggitt self-assigned this Mar 14, 2019

@mariantalla mariantalla added this to Open PR-wait for >5 successes before "Resolved" in 1.14 CI Signal Mar 15, 2019

@mariantalla mariantalla moved this from Open PR-wait for >5 successes before "Resolved" to Resolved flakes (observe closed for a week before "Resolved") in 1.14 CI Signal Mar 15, 2019

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Mar 16, 2019

@liggitt

This comment has been minimized.

Copy link
Member

liggitt commented Mar 16, 2019

agreed, I was watching the same query

@spiffxp

This comment has been minimized.

Copy link
Member

spiffxp commented Mar 16, 2019

/close

1.14 CI Signal automation moved this from Resolved flakes (observe closed for a week before "Resolved") to Open PR-wait for >5 successes before "Resolved" Mar 16, 2019

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Mar 16, 2019

@spiffxp: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@spiffxp spiffxp moved this from Open PR-wait for >5 successes before "Resolved" to Resolved (week Mar 11) in 1.14 CI Signal Mar 16, 2019

@mariantalla mariantalla moved this from Resolved (week Mar 11) to Resolved (>2 weeks old) in 1.14 CI Signal Mar 19, 2019

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.