NO-JIRA: Tolerate restarts for kubevirt external infra #3451
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@davidvossel: This pull request explicitly references no jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
area/testing
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidvossel, nunnatsa 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 |
|
/retest-required |
|
/hold Revision 221de09 was retested 3 times: holding |
openshift-ci
bot
added
the
do-not-merge/hold
|
/retest-required |
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest |
|
/test verify |
Signed-off-by: David Vossel <davidvossel@gmail.com>
davidvossel
force-pushed
the
tolerate-external-infra-restart
branch
from
221de09
to
e9904a3
Compare
|
/lgtm |
1 similar comment
|
/lgtm |
openshift-merge-bot
bot
merged commit 05168af
into
openshift:main
This PR allows the test to tolerate a single restart only for KubeVirt when running on external infra. The centralized KubeVirt infra test still does not tolerate any unexpected restarts.
The KubeVirt platform has two modes, centralized infra (where HCP and VMs run on the same OCP cluster, and external infra (Where HCP and VMs run on separate OCP clusters)
When we test external infra, we are running HCP KubeVirt running within HCP KubeVirt. This is a complex environment that is difficult to ensure has predictable performance. We occasionally see that random pods in the HCP namespace restart in this nested environment due to "Error: context deadline exceeded" being reported by the kubelet. This is likely a result of etcd latency within this environment.