-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Flake #99979 increase delay for ready state propagation #103593
Conversation
/triage accepted |
/assign @ehashman |
@@ -445,7 +445,7 @@ var _ = SIGDescribe("Probing container", func() { | |||
if readyIn < 0 { | |||
framework.Failf("Pod became ready before startupProbe succeeded") | |||
} | |||
if readyIn > 5*time.Second { | |||
if readyIn > 12*time.Second { | |||
framework.Failf("Pod became ready in %v, more than 5s after startupProbe succeeded. It means that the delay readiness probes were not initiated immediately after startup finished.", readyIn) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to update the error message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, done
/hold |
Slack discussion: https://kubernetes.slack.com/archives/C0BP8PW9G/p1625773793079000 |
at least it's not that flake 😅 |
@ehashman answers to slack points: https://hackmd.io/8BH1yq8fR9W6ZWIauHyT7w?view |
Discussed in SIG Node CI meeting 07/14 -- we will adopt the proposal outlined here https://hackmd.io/8BH1yq8fR9W6ZWIauHyT7w?view#Proposed-improvement to update the frequencies in the e2e test to decrease flakiness, and take a backlog item to fix the possible race identified here: https://hackmd.io/8BH1yq8fR9W6ZWIauHyT7w?view#Possible-race-condition-in-prober_manager @matthyx to file/update. |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming the underlying code isn't buggy, this seems like a correct adjustment to me. 25s < 30s but gives the startup probe a few tries to run and kick the readiness state.
/lgtm
/hold cancel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
let's see if this helps with flakiness
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ehashman, matthyx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Superpowers! |
What type of PR is this?
/kind flake
/priority important-soon
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #99979
Special notes for your reviewer:
As discussed during Sig-Node CI meeting: increasing delay for state propagation on busy machine.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: