e2e tests: Be resilient to temporary unavailability of k8s #28
Conversation
The tests are flaky due to leader re-elections in etcd. The following
error is logged every once in a while:
single_scan_test.go:109: rpc error: code = Unavailable desc = etcdserver: leader changed
So lets try to be more resilient in our tests.
openshift-ci-robot
added
the
size/XS
openshift-ci-robot
added
the
approved
A timeout might happen cause the cluster might be too busy. So we also need to be resilient to timeouts.
|
/test e2e-aws etcd failed again... but this time it was on the cleanup which is in the operator-sdk code. |
|
pushed operator-framework/operator-sdk#2277 to avoid issues like this in the future. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JAORMX, jhrozek 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 |
|
@JAORMX: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
The tests are flaky due to leader re-elections in etcd. The following
error is logged every once in a while:
So lets try to be more resilient in our tests.