- Infra - oVirt List Archives

[CQ]: 106413, 6 (vdsm) 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 106413,6 (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/106413/6 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/18301/

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #41 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 25 Jan '20

25 Jan '20

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

1 0

[CQ]: 105857, 5 (ovirt-engine) 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 105857,5 (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/105857/5 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/18295/

1 0

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

25 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/1080//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 106388, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 24 Jan '20

24 Jan '20

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

1 0

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

24 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106380,2 (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/106380/2 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/18283/

1 0

[CQ]: 106302, 7 (ovirt-node-ng-image) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jan '20

24 Jan '20

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

1 0

[CQ]: 106525,1 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 24 Jan '20

24 Jan '20

Change 106525,1 (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/106525/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2852/

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-4.3 - Build #146 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 24 Jan '20

24 Jan '20

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

1 0

[CQ]: 105832,17 (imgbased) failed "ovirt-master" system tests
by oVirt Jenkins 24 Jan '20

24 Jan '20

Change 105832,17 (imgbased) 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/105832/17 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18271/

1 0

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

24 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106264,15 (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/106264/15 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/18265/

1 0

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

24 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/1079//artifact/exported… Cheers, Jenkins

1 0

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

23 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106389,2 (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/106389/2 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/18259/

1 0

[CQ]: 106524, 1 (engine-db-query) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '20

23 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106524,1 (engine-db-query) failed. However, this change seems not to be the root cause for this failure. Change 106522,1 (engine-db-query) 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 106522,1 (engine-db-query) 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/106524/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106522/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2850/

1 0

[CQ]: 106522,1 (engine-db-query) failed "ovirt-4.3" system tests
by oVirt Jenkins 23 Jan '20

23 Jan '20

Change 106522,1 (engine-db-query) 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/106522/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2848/

1 0

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

23 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106399,2 (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/106399/2 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/18253/

1 0

permission to run jenkins builds after gerrit patches
by Radoslaw Szwajkowski 23 Jan '20

23 Jan '20

Hi, I've just joined Ovirt UI team. I've noticed that my patches do not trigger jenkins builds. The message is: To avoid overloading the infrastructure, a whitelist for running gerrit triggered jobs has been set in place, if you feel like you should be in it, please contact infra at ovirt dot org. Could you please add me to the whitelist? best regards, Radek

3 4

[CQ]: 106481,15 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 23 Jan '20

23 Jan '20

Change 106481,15 (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/106481/15 For failed test results see: https://jenkins.ovirt.org/job/dummy-master_change-queue-tester/297/

1 0

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

23 Jan '20

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

1 0

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

23 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106400,2 (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/106400/2 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/18247/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-7.6-el7-x86_64 #274
by jenkins＠jenkins.phx.ovirt.org 23 Jan '20

23 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-7.6-el7-x8…> Changes: ------------------------------------------ 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-updates-7.6-el7-x8…> 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 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 Commit message: "pipelines: add ruby sdk to v2 pipelines" > git rev-list --no-walk 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 # timeout=10 [system-sync_mirrors-centos-updates-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins9148914362387145744.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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/gen' + reposync_out= Build step 'Execute shell' marked build as failure

1 2

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

23 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106332,4 (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/106332/4 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/18241/

1 0

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

23 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/1078//artifact/exported… Cheers, Jenkins

1 0

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

22 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106387,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/106387/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/18235/

1 0

[CQ]: 66276a7 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 22 Jan '20

22 Jan '20

Change 66276a7 (ovirt-ansible-hosted-engine-setup) 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://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/18189/

6 13

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

22 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106357,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/106357/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/18229/

1 0

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

22 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106177,6 (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/106177/6 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/18224/

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-3.12-el7-x86_64 #2555
by jenkins＠jenkins.phx.ovirt.org 22 Jan '20

22 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-3.12-el7-x86_64…> Changes: ------------------------------------------ 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-glusterfs-3.12-el7-x86_64…> 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 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 Commit message: "pipelines: add ruby sdk to v2 pipelines" > git rev-list --no-walk 6ede28a7acb1026754efc90be18f4f2ba6ba5ea3 # timeout=10 [system-sync_mirrors-glusterfs-3.12-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3943723652288200511.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-3.12-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 glusterfs-3.12-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror glusterfs-3.12-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-3.12-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 glusterfs-3.12-el7 yum + local repo_name=glusterfs-3.12-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/glusterfs-3.12-el7 /var/www/html/repos/yum/glusterfs-3.12-el7/base + check_yum_sync_needed glusterfs-3.12-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=glusterfs-3.12-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/glusterfs-3.12-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync glusterfs-3.12-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=glusterfs-3.12-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=glusterfs-3.12-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-3.12-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: Error making cache directory: /home/jenkins/mirrors_cache/glusterfs-3.12-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/glusterfs-3.12-el7' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

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

22 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106361,4 (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/106361/4 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/18219/

1 0

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

22 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/1077//artifact/exported… Cheers, Jenkins

1 0

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

21 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106365,2 (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/106365/2 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/18214/

1 0

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

21 Jan '20

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

1 0

[JIRA] (OVIRT-2860) upgrade Gerrit to 2.16
by Evgheni Dereveanchin (oVirt JIRA) 21 Jan '20

21 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2860?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2860: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade Gerrit to 2.16 > ---------------------- > > Key: OVIRT-2860 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2860 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2860) upgrade Gerrit to 2.16
by Evgheni Dereveanchin (oVirt JIRA) 21 Jan '20

21 Jan '20

Evgheni Dereveanchin created OVIRT-2860: ------------------------------------------- Summary: upgrade Gerrit to 2.16 Key: OVIRT-2860 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2860 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: Evgheni Dereveanchin Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2859) added reviewers don't get gerrit notifications
by Evgheni Dereveanchin (oVirt JIRA) 21 Jan '20

21 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2859?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2859: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > added reviewers don't get gerrit notifications > ---------------------------------------------- > > Key: OVIRT-2859 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2859 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > As reported by [~accountid:557058:db776433-defe-4728-8cf0-8b600acd15b9] there's an issues when people added as reviewers don't receive email from gerrit. > Looking at gerrit logs this seems like a bug of some sort, logging ticket to investigate. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2859) added reviewers don't get gerrit notifications
by Evgheni Dereveanchin (oVirt JIRA) 21 Jan '20

21 Jan '20

Evgheni Dereveanchin created OVIRT-2859: ------------------------------------------- Summary: added reviewers don't get gerrit notifications Key: OVIRT-2859 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2859 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra As reported by [~accountid:557058:db776433-defe-4728-8cf0-8b600acd15b9] there's an issues when people added as reviewers don't receive email from gerrit. Looking at gerrit logs this seems like a bug of some sort, logging ticket to investigate. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

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

21 Jan '20

A system test invoked by the "ovirt-master" change queue including change 105780,3 (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/105780/3 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/18204/

1 0

Build failed in Jenkins: deploy-to_ovirt-master_tested #10110
by jenkins＠jenkins.phx.ovirt.org 21 Jan '20

21 Jan '20

See <https://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/10110/display/r…> Changes: ------------------------------------------ Started by user Michal Skrivanek Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on vm0051.workers-phx.ovirt.org (phx fc29 nested) in workspace <https://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-3wTy1bIn6t0R/agent.1940 SSH_AGENT_PID=1942 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: <https://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private…> (<https://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private…)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-master_tested] $ /bin/bash -xe /tmp/jenkins3418750445274006582.sh + [[ https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… == '' ]] + queue_name=ovirt-master + echo repo-extra-dir:master + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo 'https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar…' Pseudo-terminal will not be allocated because stdin is not a terminal. + BASE_DIR=/srv/resources/repos/ovirt/tested + PUBLISH_MD_COPIES=50 + main + local tmp_dir + mkdir -p /srv/resources/repos/ovirt/tested ++ mktemp -d /srv/resources/repos/ovirt/tested/.deploy.XXXXXXXXXX Collecting packages + tmp_dir=/srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex + trap 'rm -rf '\''/srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex'\''' EXIT HUP + echo 'Collecting packages' + collect_packages /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex + local repoman_dst=/srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex + repoman --temp-dir generate-in-repo --option main.allowed_repo_paths=/srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex --option main.on_empty_source=warn /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex add conf:stdin 2020-01-21 08:04:19,751::INFO::repoman.cmd:: 2020-01-21 08:04:19,752::INFO::repoman.cmd::Adding artifacts to the repo /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex 2020-01-21 08:04:19,752::INFO::repoman.common.repo::Adding repo extra dir master 2020-01-21 08:04:19,758::INFO::repoman.common.stores.RPM::Loading repo /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/master 2020-01-21 08:04:19,759::INFO::repoman.common.stores.RPM::Repo /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/master loaded 2020-01-21 08:04:19,763::INFO::repoman.common.stores.iso::Loading repo /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/master 2020-01-21 08:04:19,764::INFO::repoman.common.stores.iso::Repo /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/master loaded 2020-01-21 08:04:19,795::INFO::repoman.common.repo::Resolving artifact source https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… 2020-01-21 08:04:20,057::ERROR::repoman.common.sources.jenkins::URL: https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '402', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 21 Jan 2020 08:04:19 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org-ssl', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_standard-on-merge/2246/artifact/build-artifacts.build-py3.el8.x86_64//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2020-01-21 08:04:22,110::ERROR::repoman.common.sources.jenkins::URL: https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '402', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 21 Jan 2020 08:04:22 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org-ssl', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_standard-on-merge/2246/artifact/build-artifacts.build-py3.el8.x86_64//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2020-01-21 08:04:24,167::ERROR::repoman.common.sources.jenkins::URL: https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '402', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 21 Jan 2020 08:04:24 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org-ssl', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_standard-on-merge/2246/artifact/build-artifacts.build-py3.el8.x86_64//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2020-01-21 08:04:26,222::ERROR::repoman.common.sources.jenkins::URL: https://jenkins.ovirt.org/job/vdsm_standard-on-merge/2246/artifact/build-ar… Status: 404 Reason: Not Found Headers: {'cache-control': 'must-revalidate,no-cache,no-store', 'connection': 'close', 'content-length': '402', 'content-type': 'text/html;charset=iso-8859-1', 'date': 'Tue, 21 Jan 2020 08:04:26 GMT', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org-ssl', 'x-content-type-options': 'nosniff'} Body: <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 404 Not Found</title> </head> <body><h2>HTTP ERROR 404</h2> <p>Problem accessing /job/vdsm_standard-on-merge/2246/artifact/build-artifacts.build-py3.el8.x86_64//api/json. Reason: <pre> Not Found</pre></p><hr><a href="http://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT</a><hr/> </body> </html> 2020-01-21 08:04:28,225::ERROR::repoman.cmd:: 2020-01-21 08:04:28,226::ERROR::repoman.cmd::Error while adding conf:stdin 2020-01-21 08:04:28,228::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/.lago_tmp/tmptZ8iRf/tmpbk83d8 2020-01-21 08:04:28,228::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex/.lago_tmp/tmptZ8iRf + rm -rf /srv/resources/repos/ovirt/tested/.deploy.lH2RkLfGex Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 1942 killed; [ssh-agent] Stopped.

1 1

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

21 Jan '20

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

1 0

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

21 Jan '20

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

1 0

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

21 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106363,3 (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/106363/3 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/18199/

1 0

[CQ]: 106362, 1 (java-client-kubevirt) failed "ovirt-master" system tests
by oVirt Jenkins 21 Jan '20

21 Jan '20

Change 106362,1 (java-client-kubevirt) 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/106362/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18194/

1 0

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

21 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/1076//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 105942,1 (ovirt-host) failed "ovirt-master" system tests
by oVirt Jenkins 20 Jan '20

20 Jan '20

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

1 0

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

20 Jan '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.…> Changes: ------------------------------------------ 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 7ea39d9c23b94da5498c23a574c14b8403ef8ee5 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 7ea39d9c23b94da5498c23a574c14b8403ef8ee5 Commit message: "gate: Fix suit cloning in container" > git rev-list --no-walk 7ea39d9c23b94da5498c23a574c14b8403ef8ee5 # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2256290304568313237.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: failure: repodata/be198d32d786c933beb06e141f7f49d7b9671df70ecb09f05c39370d498a5f57-primary.sqlite.bz2 from centos-sclo-rh-release-7.6-el7: [Errno 256] No more mirrors to try. http://vault.centos.org/7.6.1810/sclo/x86_64/rh/repodata/be198d32d786c933be…: [Errno 16] error setting timestamp on file /home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/be198d32d786c933beb06e141f7f49d7b9671df70ecb09f05c39370d498a5f57-primary.sqlite.bz2 from http://vault.centos.org/7.6.1810/sclo/x86_64/rh/repodata/be198d32d786c933be…, OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-sclo-rh-release-7.6-el7/be198d32d786c933beb06e141f7f49d7b9671df70ecb09f05c39370d498a5f57-primary.sqlite.bz2' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

OST CI: Time issue?
by Yedidyah Bar David 20 Jan '20

20 Jan '20

Hi all, I looked at failure of [1]. It timed out while waiting for the engine to be up, after restarting the engine VM. lago.log [2] has: 2020-01-20 04:16:06,026::008_restart_he_vm.py::_start_he_vm::173::root::INFO::Starting VM... ... 2020-01-20 04:16:09,823::008_restart_he_vm.py::_start_he_vm::178::root::INFO::Waiting for VM to be UP... ... 2020-01-20 04:16:25,113::008_restart_he_vm.py::_start_he_vm::186::root::INFO::VM is UP. 2020-01-20 04:16:25,113::008_restart_he_vm.py::_wait_for_engine_health::190::root::INFO::Waiting for engine to start... ... Then there is a loop of running 'hosted-engine --vm-status --json' and parsing the status, specifically checking the health. The health status does not change until the timeout (after 10 minutes), but after 'vm', there is 'detail', which does change. First one is 'Powering up': 2020-01-20 04:16:25,113::ssh.py::ssh::89::lago.ssh::DEBUG::Command 9ef791c0 on lago-he-basic-role-remote-suite-4-3-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5199 (Sun Jan 19 23:16:24 2020)\nhost-id=1\nscore=2400\nvm_conf_refresh_time=5199 (Sun Jan 19 23:16:24 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-role-remote-suite-4-3-host-0.lago.local", "host-id": 1, "engine-status": {"reason": "bad vm status", "health": "bad", "vm": "up", "detail": "Powering up"}, "score": 2400, "stopped": false, "maintenance": false, "crc32": "e7f42f2a", "local_conf_timestamp": 5199, "host-ts": 5199}, "2": {"conf_on_shared_storage": true, "live-data": false, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5190 (Sun Jan 19 23:16:15 2020)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=5190 (Sun Jan 19 23:16:15 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-role-remote-suite-4-3-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "c3657e8b", "local_conf_timestamp": 5190, "host-ts": 5190}, "global_maintenance": true} ... Then a few similar ones, last one is from '2020-01-20 04:17:22,980', and then it changes to 'Up': 2020-01-20 04:17:27,517::ssh.py::ssh::89::lago.ssh::DEBUG::Command c426f53a on lago-he-basic-role-remote-suite-4-3-host-0 output: {"1": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5259 (Sun Jan 19 23:17:24 2020)\nhost-id=1\nscore=2928\nvm_conf_refresh_time=5259 (Sun Jan 19 23:17:24 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-role-remote-suite-4-3-host-0.lago.local", "host-id": 1, "engine-status": {"reason": "failed liveliness check", "health": "bad", "vm": "up", "detail": "Up"}, "score": 2928, "stopped": false, "maintenance": false, "crc32": "08d4bfe1", "local_conf_timestamp": 5259, "host-ts": 5259}, "2": {"conf_on_shared_storage": true, "live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=5250 (Sun Jan 19 23:17:16 2020)\nhost-id=2\nscore=3400\nvm_conf_refresh_time=5251 (Sun Jan 19 23:17:16 2020)\nconf_on_shared_storage=True\nmaintenance=False\nstate=GlobalMaintenance\nstopped=False\n", "hostname": "lago-he-basic-role-remote-suite-4-3-host-1", "host-id": 2, "engine-status": {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "ab277249", "local_conf_timestamp": 5251, "host-ts": 5250}, "global_maintenance": true} /var/log/messages of the engine vm [3] has: Jan 19 23:17:57 lago-he-basic-role-remote-suite-4-3-engine kernel: Initializing cgroup subsys cpuset Meaning, the first line after the reboot has a timestamp that's almost 2 minutes after starting the VM. That's a long time. That's half a minute after detail changed to 'Up', above (no idea where we take this 'detail' from, though). Then, first line that is not from the kernel: Jan 19 23:17:58 lago-he-basic-role-remote-suite-4-3-engine systemd[1]: systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 -SECCOMP +BLKID +ELFUTILS +KMOD +IDN) then it starts lots of services, and then: Jan 19 23:20:31 lago-he-basic-role-remote-suite-4-3-engine systemd: Started oVirt Engine websockets proxy. Jan 19 23:20:33 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: Selected source 45.33.103.94 Jan 19 23:20:37 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: System clock wrong by 3.919225 seconds, adjustment started Jan 19 23:20:37 lago-he-basic-role-remote-suite-4-3-engine systemd: Time has been changed Jan 19 23:20:37 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: System clock was stepped by 3.919225 seconds Jan 19 23:20:38 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: Selected source 129.250.35.250 Jan 19 23:20:43 lago-he-basic-role-remote-suite-4-3-engine cloud-init: Cloud-init v. 18.5 running 'modules:config' at Mon, 20 Jan 2020 04:20:39 +0000. Up 182.82 seconds. and later: Jan 19 23:21:32 lago-he-basic-role-remote-suite-4-3-engine systemd: Started Update UTMP about System Runlevel Changes. Jan 19 23:21:32 lago-he-basic-role-remote-suite-4-3-engine systemd: Startup finished in 22.344s (kernel) + 32.237s (initrd) + 3min 815ms (userspace) = 3min 55.397s. Jan 19 23:21:43 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: Selected source 206.55.191.142 Jan 19 23:23:52 lago-he-basic-role-remote-suite-4-3-engine chronyd[872]: Selected source 129.250.35.250 Jan 19 23:26:32 lago-he-basic-role-remote-suite-4-3-engine systemd: Created slice User Slice of root. engine.log's [4] first line after the reboot is: 2020-01-19 23:26:18,251-05 INFO [org.ovirt.engine.core.uutils.config.ShellLikeConfd] (ServerService Thread Pool -- 103) [] Loaded file '/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf'. which is a mere 40 seconds before the timeout, and server.log's [5] first line is: 2020-01-19 23:23:13,392-05 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "apidoc.war" (runtime-name: "apidoc.war") which is a 3 minutes before that. I do not know much about what the engine does during its startup, and how the logs should look, and how long it should take between startup and a working health page. If this all looks normal, then perhaps we should simply give it more than 10 minutes. Otherwise, there is either heavy load on the infra, or perhaps some NTP problems. Anyone has a clue? Anyway, now pushed a patch [6] to allow up to 20 minutes, at least to reduce the noise. Thanks and best regards, [1] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… [2] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… [3] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… [4] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… [5] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… [6] https://gerrit.ovirt.org/106411 -- Didi

1 0

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

20 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106329,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/106329/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/18181/

1 0

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

20 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/1075//artifact/exported… Cheers, Jenkins

1 0

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

19 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106392,2 (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/106392/2 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/18178/

1 0

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

19 Jan '20

A system test invoked by the "ovirt-master" change queue including change 106376,1 (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/106376/1 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/18177/

1 0