- Infra - oVirt List Archives

[CQ]: 106462, 1 (imgbased) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jan '20

28 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106462,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 105832,17 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 105832,17 (imgbased) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106462/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/105832/17 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18391/

1 0

Build failed in Jenkins: system-sync_mirrors-epel-s390x-el7-s390x #216
by jenkins＠jenkins.phx.ovirt.org 28 Jan '20

28 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/216/…> Changes: [Artur Socha] vdsm-jsonrpc-java: enable STDCI v2 ------------------------------------------ Started by user Shlomi Zidmi Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-epel-s390x-el7-s390x/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 49e38466ef907b2a6ed4f77f20d7b86ed5b76e96 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 49e38466ef907b2a6ed4f77f20d7b86ed5b76e96 Commit message: "vdsm-jsonrpc-java: enable STDCI v2" > git rev-list --no-walk b902a1b18f01e5cdc3bf8239ec535a3373405803 # timeout=10 [system-sync_mirrors-epel-s390x-el7-s390x] $ /bin/bash -xe /tmp/jenkins832747344328905547.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-s390x-el7 s390x jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror epel-s390x-el7 s390x jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror epel-s390x-el7 s390x jenkins/data/mirrors-reposync.conf + local repo_name=epel-s390x-el7 + local repo_archs=s390x + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs epel-s390x-el7 yum + local repo_name=epel-s390x-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/epel-s390x-el7 /var/www/html/repos/yum/epel-s390x-el7/base + check_yum_sync_needed epel-s390x-el7 s390x jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=epel-s390x-el7 + local repo_archs=s390x + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/epel-s390x-el7 ++ IFS=, ++ echo s390x + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync epel-s390x-el7 s390x jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=epel-s390x-el7 ++ local repo_arch=s390x ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=epel-s390x-el7 --arch=s390x --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/epel-s390x-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: failure: repodata/d9dff1cf22c99f84c309e43e1b51d33ec2f6ecb40444a3a3b93088b18f4f661c-primary.sqlite.bz2 from epel-s390x-el7: [Errno 256] No more mirrors to try. http://download.sinenomine.net/clefos/epel7/repodata/d9dff1cf22c99f84c309e4…: [Errno 14] HTTP Error 404 - Not Found + reposync_out= Build step 'Execute shell' marked build as failure

1 15

[CQ]: 106462, 1 (imgbased) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jan '20

28 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106462,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 105832,17 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 105832,17 (imgbased) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106462/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/105832/17 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18385/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #290
by jenkins＠jenkins.phx.ovirt.org 28 Jan '20

28 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> Changes: [Barak Korren] Drop Minishift fixture [Barak Korren] Fix EL7 mock on FC30 nodes ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 806378e258ba8a588f7ca30acf71851f0ce1eb72 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 806378e258ba8a588f7ca30acf71851f0ce1eb72 Commit message: "Fix EL7 mock on FC30 nodes" > git rev-list --no-walk e85f8b546934caae99b9ef7c991f22a6697bbed2 # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins5348462502121556026.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs centos-sclo-rh-release-7.6-el7 yum + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7 /var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base + check_yum_sync_needed centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-sclo-rh-release-7.6-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-sclo-rh-release-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-sclo-rh-release-7.6-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=centos-sclo-rh-release-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-sclo-rh-release-7.6-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/packages error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/packages' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 524d3eb (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 28 Jan '20

28 Jan '20

A system test invoked by the "ovirt-master" change queue including change 524d3eb (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 66276a7 (ovirt-ansible- hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 66276a7 (ovirt-ansible-hosted- engine-setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/524d3eb2f… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/66276a7b4… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18379/

1 0

oVirt infra daily report - unstable production jobs - 1083
by jenkins＠jenkins.phx.ovirt.org 28 Jan '20

28 Jan '20

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

1 0

[CQ]: 106434, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jan '20

27 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106434,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106280,6 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106434/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18373/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #195 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jan '20

27 Jan '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/195/ Build Name: #195 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 1

[CQ]: 106538,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 27 Jan '20

27 Jan '20

Change 106538,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/106538/2 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/307/

1 0

Bug not moved to ON_QA because of nonexisting tag
by Andrej Krejcir 27 Jan '20

27 Jan '20

Hi, I got a comment on one of my bugs[1], which looks like a bug in the script. INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.4.0' doesn't contain patch ' https://gerrit.ovirt.org/104859'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/o… But the tag 'ovirt-engine-4.4.0', does not exist in the git repo. I'm also getting nonsense warnings on other bugs like [2]. [1] - https://bugzilla.redhat.com/show_bug.cgi?id=1678007#c5 [2] - https://bugzilla.redhat.com/show_bug.cgi?id=1762281#c10 Regards, Andrej

1 0

[oVirt CI] standard-enqueue - Build #26485 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jan '20

27 Jan '20

Build: https://jenkins.ovirt.org/job/standard-enqueue/26485/ Build Name: #26485 Build Description: Gerrit: 106566 - ovirt-engine-api-model (4.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/106566 - title: Update CHANGES.adoc for release 4.3.30 - project: ovirt-engine-api-model - branch: model_4.3 - author: Ori Liel <oliel(a)redhat.com>

1 1

[CQ]: 106144, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jan '20

27 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106144,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 104391,14 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 104391,14 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106144/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/104391/14 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18367/

1 0

[CQ]: 106424, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Jan '20

27 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106424,3 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106280,6 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106424/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18361/

1 0

[CQ]: 106453,4 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 27 Jan '20

27 Jan '20

Change 106453,4 (cockpit-ovirt) 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/106453/4 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18355/

1 0

oVirt infra daily report - unstable production jobs - 1082
by jenkins＠jenkins.phx.ovirt.org 27 Jan '20

27 Jan '20

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

1 0

[CQ]: 106448, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jan '20

26 Jan '20

Change 106448,3 (ovirt-hosted-engine-ha) 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/106448/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18349/

1 0

[CQ]: 106455, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '20

26 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106455,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106280,6 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106455/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18343/

1 0

[CQ]: 106533, 1 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '20

26 Jan '20

A system test invoked by the "dummy-master" change queue including change 106533,1 (jenkins) failed. However, this change seems not to be the root cause for this failure. Change 106529,1 (jenkins) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106529,1 (jenkins) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106533/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106529/1 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/302/

1 0

[oVirt Jenkins] deploy-to-gated-dummy-master - Build #189 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Build: https://jenkins.ovirt.org/job/deploy-to-gated-dummy-master/189/ Build Name: #189 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 2

[CQ]: 106444, 2 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '20

26 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106444,2 (ovirt-host) failed. However, this change seems not to be the root cause for this failure. Change 105942,1 (ovirt-host) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 105942,1 (ovirt-host) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106444/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/105942/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18337/

1 0

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 1474 - Still Failing!
by Yedidyah Bar David 26 Jan '20

26 Jan '20

On Sun, Jan 26, 2020 at 4:33 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1474/ https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/1474… : + yum install '--disablerepo=*' --enablerepo=ovirt-master-snapshot-static-el7,sac-gluster-ansible-el7,glusterfs-6-el7,centos-updates-el7,centos-base-el7,centos-extras-el7,epel-el7,centos-ovirt-4.4-testing-el7,centos-ovirt-common-el7,centos-qemu-ev-testing-el7,centos-opstools-testing-el7,centos-sclo-rh-release-el7 -y yum-utils Error: Error writing to file /dev/shm/yum/x86_64/7/epel-el7/gen/primary_db.sqlite: [Errno 28] No space left on device Any idea? Thanks, > Build Number: 1474 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #1464 > [Martin Perina] basic master: Increase iscsi NOOP timeout to 30 sec > > > Changes for Build #1465 > [Galit Rosenthal] Move HE suite to centos8 > > > Changes for Build #1466 > [Galit Rosenthal] Move HE suite to centos8 > > > Changes for Build #1467 > [jenkins CI] Auto create ovirt-4.3-cq > > > Changes for Build #1468 > [jenkins CI] Auto create ovirt-4.3-cq > > [Barak Korren] gate: Fix suit cloning in container > > > Changes for Build #1469 > [Michal Skrivanek] add AdvancedVirt repo > > > Changes for Build #1470 > [Martin Perina] basic master: Update all packages when setting up a host > > [Sandro Bonazzola] pipelines: add ruby sdk to v2 pipelines > > > Changes for Build #1471 > [Martin Perina] basic master: Update all packages when setting up a host > > > Changes for Build #1472 > [Martin Perina] basic master: Update all packages when setting up a host > > [Barak Korren] Ensure Python scripts in toolbox work > > [Barak Korren] Add usrc.py to the toolbox > > > Changes for Build #1473 > [Galit Rosenthal] Remove suites fail more than a month from check patch > > > Changes for Build #1474 > [Galit Rosenthal] Remove suites fail more than a month from check patch > > [Martin Perina] mock: Enable maven and pki-deps modules on EL8 > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. -- Didi

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0148.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0043.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0012.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0090.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0061.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0062.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0037.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0038.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0098.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0015.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0011.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0013.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0008.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0007.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0042.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0087.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0207.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0219.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0220.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0218.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

Failed to run project_setup.sh for: #4200 jenkins [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 vm0216.workers-phx.ovirt.org.

1 0

[CQ]: 106366, 5 (java-client-kubevirt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '20

26 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106366,5 (java-client-kubevirt) failed. However, this change seems not to be the root cause for this failure. Change 106362,1 (java-client-kubevirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106362,1 (java-client-kubevirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106366/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106362/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18331/

1 0

[CQ]: 106426, 1 (java-client-kubevirt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '20

26 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106426,1 (java-client-kubevirt) failed. However, this change seems not to be the root cause for this failure. Change 106362,1 (java-client-kubevirt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106362,1 (java-client-kubevirt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106426/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106362/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18325/

1 0

oVirt infra daily report - unstable production jobs - 1081
by jenkins＠jenkins.phx.ovirt.org 26 Jan '20

26 Jan '20

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

1 0

[CQ]: 106443,1 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 25 Jan '20

25 Jan '20

Change 106443,1 (ovirt-engine-sdk) 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/106443/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18319/

1 0

[CQ]: 106354, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 25 Jan '20

25 Jan '20

Change 106354,1 (ovirt-engine-api-model) 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/106354/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18313/

1 0

[CQ]: 106529,1 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 25 Jan '20

25 Jan '20

Change 106529,1 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/106529/1 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/300/

1 0

[CQ]: 106430, 2 (ovirt-system-tests) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '20

25 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106430,2 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106384,1 (ovirt-system-tests) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 106384,1 (ovirt-system-tests) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/106430/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106384/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18307/

1 0