-
Notifications
You must be signed in to change notification settings - Fork 1k
Retry when getting the pod_environment_secret #1777
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
Conversation
I see the e2e failure. Wondering if it's flakiness? The error doesn't seem related to my changes, but I could be wrong... |
LGTM. Thanks. Yeah e2e tests on github are very flaky. You can ignore them. |
03b56c0
to
1dcd37a
Compare
2eea279
to
6246eb5
Compare
6246eb5
to
3814e73
Compare
Done. I had a lot of trouble trying to run the tests. I couldn't get them to pass even in the master branch. |
f0f432b
to
c88aac5
Compare
I was able to get the unit tests running after some trouble. - I added to the |
c88aac5
to
8e362b8
Compare
pkg/cluster/k8sres_test.go
Outdated
ResourceCheckTimeout: time.Duration(10), | ||
}, | ||
}, | ||
err: fmt.Errorf(`could not read Secret PodEnvironmentSecretName: still failing after 3 retries: secret.core "idonotexist" not found`), |
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.
err: fmt.Errorf(`could not read Secret PodEnvironmentSecretName: still failing after 3 retries: secret.core "idonotexist" not found`), | |
err: fmt.Errorf("could not read Secret PodEnvironmentSecretName: still failing after 3 retries: secret.core %q not found", "idonotexist"), |
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.
Would make sense to have a constant for the name, check #1794
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.
Also would be nice to don't hardcode 3
as its 10/3
, i.e. ResourceCheckTimeout/ResourceCheckInterval
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.
I've added this commit, is that what you were looking for?
4ea0954
to
6635227
Compare
👍 |
1 similar comment
👍 |
Thanks @snarlysodboxer for your contribution! |
See #1776.
Not sure if this is how you would want this implemented, but it didn't take long so I thought I'd get the conversation going. It's unclear to me how retries here might play into retries at higher levels.
Should the interval or timeout be configurable? Should it retry indefinitely?