October 2018 - Infra - Ovirt List Archives

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2300 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2300 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-2542) several failures failures on host not being available - possible networking issue

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jir... ] Dafna Ron updated OVIRT-2542: ----------------------------- Labels: ost_failures (was: ost_failures ost_race) > several failures failures on host not being available - possible networking issue > ---------------------------------------------------------------------------------- > > Key: OVIRT-2542 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2542 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > I have noticed that there are several issues that had failed recently with host not available. > the changes are not directly related to the issue and I cannot see anything in engine to suggest that there is a problem. > it could either be a network issue, a network test suite issue or infra related issue. > I am opening this Jira so we can follow all the failures and see if we can find a common denominator -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

5 years, 11 months

1
0
0 / 0

[JIRA] (OVIRT-2542) several failures failures on host not being available - possible networking issue

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2542?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2542: ---------------------------------- https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3378/ > several failures failures on host not being available - possible networking issue > ---------------------------------------------------------------------------------- > > Key: OVIRT-2542 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2542 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > I have noticed that there are several issues that had failed recently with host not available. > the changes are not directly related to the issue and I cannot see anything in engine to suggest that there is a problem. > it could either be a network issue, a network test suite issue or infra related issue. > I am opening this Jira so we can follow all the failures and see if we can find a common denominator -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100094)

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2298 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2298 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2298 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2298 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

[CQ]: 95000,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 95000,2 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95000/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3378/

5 years, 11 months

1
0
0 / 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #2298 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 ovirt-srv04.phx.ovirt.org-container-1.

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra October 2018