[JENKINS] Failed to setup proejct
kubevirt_containerized-data-importer_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#1473 containerized-data-importer [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-b31jr.
5 years, 8 months
[JIRA] (OVIRT-2566) make network suite blocking
by Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ]
Eyal Edri commented on OVIRT-2566:
----------------------------------
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)
> make network suite blocking
> ---------------------------
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
> 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-te...
> 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".
> [~gbenhaim(a)redhat.com], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
5 years, 8 months
[JIRA] (OVIRT-2566) make network suite blocking
by danken (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2566?page=com.atlassian.jir... ]
danken commented on OVIRT-2566:
-------------------------------
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.
> make network suite blocking
> ---------------------------
>
> Key: OVIRT-2566
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2566
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: OST
> Reporter: danken
> Assignee: infra
> Priority: High
>
> 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-te...
> 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".
> [~gbenhaim(a)redhat.com], what should be done to make this happen?
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-c2m45.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-7zxnk.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-0cq3b.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3684 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-90n54.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-62gsk.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-9fvmp.
5 years, 8 months
[JENKINS] Failed to setup proejct
kubevirt_kubevirt_standard-check-pr
by jenkins@jenkins.phx.ovirt.org
Failed to run project_setup.sh for:
#3683 kubevirt [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on openshift-kubevirt-org-4rfdb.
5 years, 8 months