-
Notifications
You must be signed in to change notification settings - Fork 832
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
use newer certmanager #1298
use newer certmanager #1298
Conversation
Fri Dec 20 12:27:25 UTC 2019 impatient try |
/ok-to-test |
Fri Dec 20 12:27:37 UTC 2019 impatient try |
Fri Dec 20 12:28:51 UTC 2019 impatient try |
Fri Dec 20 12:28:58 UTC 2019 impatient try |
Fri Dec 20 12:29:13 UTC 2019 impatient try |
/test integration |
Fri Dec 20 12:56:10 UTC 2019 impatient try |
Hmm, the e2e errors I'm seeing from server are |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cliveseldon 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 |
Problem in the cluster is coming from the istio rollout
|
/test integration |
Fri Dec 20 15:01:51 UTC 2019 impatient try |
Fri Dec 20 15:35:08 UTC 2019 impatient try |
Fri Dec 20 15:35:11 UTC 2019 impatient try |
Fri Dec 20 15:36:47 UTC 2019 impatient try |
Fri Dec 20 15:36:49 UTC 2019 impatient try |
/test integration |
Fri Dec 20 15:39:55 UTC 2019 impatient try |
The problem with the rollout status on istio-ingressgateway seems to be that you can eventually lose the watch. I did an exec into the container and pointed my shell at the kind context inside. This revealed several stuck istio pods: I then looked at the logs for the istio-galley pod and found the error:
So I guess the problem is insufficient ephemeral storage |
Have removed old jobs that may be using disk space. Trying again. |
/test integration |
Fri Dec 20 16:14:46 UTC 2019 impatient try |
After removing all the old completed pods, the only failure was the usual intermittent 503 problem. |
Fri Dec 20 16:59:44 UTC 2019 impatient try |
Fri Dec 20 16:59:49 UTC 2019 impatient try |
/test integration |
Fri Dec 20 17:05:46 UTC 2019 impatient try |
Now seeing However it did eventually finish and again only one failure... an intermittent ambassador 503 in one of the rolling update tests (this time test_rolling_update2) |
/test integration |
Fri Dec 20 17:51:11 UTC 2019 impatient try |
fixes #1262