November 2019 - Infra - Ovirt List Archives

oVirt infra daily report - unstable production jobs - 999

by jenkins＠jenkins.phx.ovirt.org

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/999//artifact/exported... Cheers, Jenkins

5 years

1
0
0 / 0

[CQ]: 104415, 4 (ovirt-engine-ui-extensions) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 104415,4 (ovirt-engine-ui-extensions) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/104415/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2397/

5 years

1
0
0 / 0

[CQ]: 104415, 4 (ovirt-engine-ui-extensions) failed "ovirt-master" system tests

by oVirt Jenkins

Change 104415,4 (ovirt-engine-ui-extensions) is probably the reason behind recent system test failures in the "ovirt-master" 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/104415/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16741/

5 years

1
0
0 / 0

[CQ]: 104310, 15 (ovirt-node-ng-image) failed "ovirt-master" system tests

by oVirt Jenkins

Change 104310,15 (ovirt-node-ng-image) is probably the reason behind recent system test failures in the "ovirt-master" 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/104310/15 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16738/

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #13789 vdsm [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 vm0093.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[CQ]: 104364,3 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

Change 104364,3 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" 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/104364/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16734/

5 years

1
0
0 / 0

[JIRA] (OVIRT-2822) qemu is configured with the wrong uid in our Jenkins slaves

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2822?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-2822: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > qemu is configured with the wrong uid in our Jenkins slaves > ----------------------------------------------------------- > > Key: OVIRT-2822 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2822 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > Our puppet script creates the qemu uid before qemu is installed, hence it's created with the wrong UID which is being assigned to it. > We should either create QEMU with the correct UID (107) or let QEMU's install scripts to do their job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years

1
0
0 / 0

[JIRA] (OVIRT-2822) qemu is configured with the wrong uid in our Jenkins slaves

by Daniel Belenky (oVirt JIRA)

Daniel Belenky created OVIRT-2822: ------------------------------------- Summary: qemu is configured with the wrong uid in our Jenkins slaves Key: OVIRT-2822 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2822 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Our puppet script creates the qemu uid before qemu is installed, hence it's created with the wrong UID which is being assigned to it. We should either create QEMU with the correct UID (107) or let QEMU's install scripts to do their job. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #1227 ovirt-engine [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 vm0006.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #13712 vdsm [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 vm0093.workers-phx.ovirt.org.

5 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra November 2019