]
Barak Korren commented on OVIRT-2498:
-------------------------------------
[~pkotas] ok, I see its failing in the docketr-cleaup script... hmm.. we'll need to
debug that...
Can you please open a specific ticket on that and include logs and any other specific
information that can help us figure out why it may be failing there... (What containers
might be on the machine that its failing to remove...)
But that is not what is causing all the failures right? We already fixed a couple of
issues with that script...
Failing KubeVirt CI
-------------------
Key: OVIRT-2498
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-2498
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Petr Kotas
Assignee: infra
Hi,
I am working on fixing the issues on the KubeVirt e2e test suites. This
task is directly related to unstable CI, due to unknown errors.
The progress is reported in the CNV trello:
https://trello.com/c/HNXcMEQu/161-epic-improve-ci
I am creating this issue since the KubeVirt experience random timeouts on
random tests most of the times when test suites run.
The issue from outside is showing as timeouts on difference part of tests.
Sometimes the tests fails in set up phase, again due to random timeout.
The example in the link bellow timed out for network connection on
localhost.
[check-patch.k8s-1.11.0-dev.el7.x86_64]
requests.exceptions.ReadTimeout:
UnixHTTPConnectionPool(host='localhost', port=None): Read timed out.
(read timeout=60)
Example of failing test suites is here
https://jenkins.ovirt.org/job/kubevirt_kubevirt_standard-check-pr/1916/co...
The list of errors related to the failing CI can be found in my notes
https://docs.google.com/document/d/1_ll1DOMHgCRHn_Df9i4uvtRFyMK-bDCHEeGfJ...
I am not sure whether KubeVirt already shared the resource requirements, so
I provide short summary:
*Resources for KubeVirt e2e tests:*
- at least 12GB of RAM - we start 3 nodes (3 docker images) each require
4GB of RAM
- exposed /dev/kvm to enable native virtualization
- cached images, since these are used to build the test cluster:
- kubevirtci/os-3.10.0-crio:latest
- kubevirtci/os-3.10.0-multus:latest
- kubevirtci/os-3.10.0:latest
- kubevirtci/k8s-1.10.4:latest
- kubevirtci/k8s-multus-1.11.1:latest
- kubevirtci/k8s-1.11.0:latest
How can we overcome this? Can we work together to build a suitable
requirements for running the tests so it passes each time?
Kind regards,
Petr Kotas