Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

make network suite blocking

Description

The network suite is executing nightly for almost a year. It has a caring team that tends to it, and it does not have false positives.
Currently, it currently fails for a week on the 4.2 branch, but it is due to a production code bug.
https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_network-suite-4.2/

I would like to see this suite escalated to the importance of the basic suite, making it a gating condition for marking a collection of packages as "tested".

, what should be done to make this happen?

Activity

Show:

Nir Soffer March 4, 2019 at 9:41 PM

On Mon, Nov 5, 2018 at 8:59 AM danken (oVirt JIRA) <

I'm ok with this only if it will gate only vdsm-network package, and it
will run in parallel, so
it does not slow down OST run.

For basic suite, we have too many random failures, so I don't think it is
useful, and we should
make it optional.

Nir

Eyal Edri March 4, 2019 at 1:24 PM

We still need to allocate bare metal to run it on each CQ run, and I'm not
sure we have available resources for it, pretty sure we don't have since
KubeVirt took half of the hosts.

On Mon, Mar 4, 2019 at 2:09 PM danken (oVirt JIRA) <

–

Eyal edri

MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R&D

Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)

danken March 4, 2019 at 11:49 AM

Is there news here? Would you try adding it?

A benefit for sequential execution, is that you don't need to waste resources on the network suite if the basic suite has finished successfully.

Barak Korren November 5, 2018 at 7:54 AM
Edited

To save time I prefer the network suite to run in parallel to the basic suite.

Its not a matter of preference - there is no other option.

WDYT? will this prolong our CQ iterations?

Also how are we with capacity? Do we have enough? would this be a good candidate to run in a container?

cc:

danken November 5, 2018 at 7:41 AM

https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/buildTimeTrend shows that it runs for 44-48 minutes.

https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/buildTimeTrend runs slightly quicker (41-45 minutes)

To save time I prefer the network suite to run in parallel to the basic suite.

Barak Korren November 5, 2018 at 7:04 AM

how long does it take the suit to run?

danken November 5, 2018 at 7:00 AM

Details

Assignee

Reporter

Components

Priority

Created November 5, 2018 at 6:59 AM
Updated September 1, 2019 at 7:52 AM