-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Wait for kubernetes components on soft start #8199
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: priyawadhwa 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 |
/ok-to-test |
I noticed that TestComponentHealth/parallel/ComponentHealth was failing with this error: ``` Error apiserver status: https://172.17.0.3:8441/healthz returned error 500: [-]etcd failed: reason withheld ``` but by the time post mortem logs were printed the etcd container was up and running. I think this test occasionally fails because apiserver healthz is not yet returning a 200 status when we run the test. We wait for healthz to return 200 on regular start, but not on soft start, which we run in `TestFunctional`. This PR adds a retry, which should give the apiserver time to become healthy.
210c8c3
to
cc40795
Compare
Codecov Report
@@ Coverage Diff @@
## master #8199 +/- ##
=======================================
Coverage 34.59% 34.59%
=======================================
Files 147 147
Lines 9381 9381
=======================================
Hits 3245 3245
Misses 5739 5739
Partials 397 397 |
kvm2 Driver Times for Minikube (PR 8199): [65.670369753 59.47718224399999 64.740622071] Averages Time Per Log
docker Driver Times for Minikube (PR 8199): [26.041959337999998 25.815322612 25.46038041] Averages Time Per Log
|
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 think it is better that we solve this in the code, rather the integraiton test,
the wait=all be making sure the api server is up !
if it is not, we need a new wait-components that waits for all
@medyagh |
kvm2 Driver Times for Minikube (PR 8199): [68.338790635 69.342338672 65.71761839100002] Averages Time Per Log
docker Driver Times for Minikube (PR 8199): [28.934048177 28.356889229000004 26.991050653000002] Averages Time Per Log
|
I noticed that TestComponentHealth/parallel/ComponentHealth was failing with this error:
but by the time post mortem logs were printed the etcd container was up and running.
I think this test occasionally fails because apiserver healthz is not yet returning a 200 status when we run the test. We wait for healthz to return 200 on regular start, but not on soft start, which we run in
TestFunctional
.With this PR, the --wait flag will be respected on soft start, so now we can be sure the apiserver is healthy before running this test
closes #8014