November 2019 - Infra - Ovirt List Archives

[CQ]: 105111,2 (ovirt-system-tests) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 105111,2 (ovirt-system-tests) 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/105111/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2567/

5 years

1
0
0 / 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #47 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

Build: http://jenkins.ovirt.org/job/deploy-to-gated-ovirt-4.3/47/ Build Name: #47 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

5 years

1
0
0 / 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #103

by jenkins＠jenkins.phx.ovirt.org

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x...> Changes: [Artur Socha] vdsm-jsonrpc-java: branch ovirt-4.3 for '4.3' [Artur Socha] vdsm-jsonrpc-java: build for fc30 added ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x...> 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 9c8516b45a7ce7d7b52dcb6581e1d9ebdf3b4223 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9c8516b45a7ce7d7b52dcb6581e1d9ebdf3b4223 Commit message: "vdsm-jsonrpc-java: build for fc30 added" > git rev-list --no-walk 4f20262d909b3fe1ea5b75b042d7077f8740bc3b # timeout=10 [system-sync_mirrors-centos-updates-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1985040177696596464.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-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-updates-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-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-updates-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-updates-7.6-el7 yum + local repo_name=centos-updates-7.6-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-updates-7.6-el7 /var/www/html/repos/yum/centos-updates-7.6-el7/base + check_yum_sync_needed centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-updates-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-updates-7.6-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-updates-7.6-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-updates-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-updates-7.6-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-updates-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 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7' + reposync_out= Build step 'Execute shell' marked build as failure

5 years

1
1
0 / 0

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

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #14965 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 vm0009.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[CQ]: 105028, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-master" change queue including change 105028,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 103437,35 (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 103437,35 (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/105028/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/103437/35 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17382/

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #325 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #324 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #323 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

5 years

1
0
0 / 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-on-merge

by jenkins＠jenkins.phx.ovirt.org

Failed to run project_setup.sh for: #322 ovirt-imageio [check-merged]. 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 vm0009.workers-phx.ovirt.org.

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: #1894 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 vm0009.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