- Infra - oVirt List Archives

[CQ]: 104529,14 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 05 Dec '19

05 Dec '19

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

1 0

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

05 Dec '19

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

1 0

[CQ]: 105145, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '19

05 Dec '19

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

1 0

[CQ]: 105333,2 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 05 Dec '19

05 Dec '19

Change 105333,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/105333/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2630/

1 0

[CQ]: 105333, 2 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '19

05 Dec '19

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

1 0

[oVirt Jenkins] deploy-to-gated-ovirt-master - Build #67 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Dec '19

05 Dec '19

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

1 0

[CQ]: 105350, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '19

05 Dec '19

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

1 0

[JIRA] (OVIRT-2846) java-client-kubevirt mirror to github
by Piotr Kliczewski (oVirt JIRA) 05 Dec '19

05 Dec '19

Piotr Kliczewski created OVIRT-2846: --------------------------------------- Summary: java-client-kubevirt mirror to github Key: OVIRT-2846 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2846 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Piotr Kliczewski Assignee: infra Hi, Please enable mirroring of java-client-kubevirt to github - ovirt org. Thanks, Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100115)

1 0

[CQ]: 105196, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '19

05 Dec '19

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

1 0

oVirt infra daily report - unstable production jobs - 1029
by jenkins＠jenkins.phx.ovirt.org 05 Dec '19

05 Dec '19

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

1 0

[CQ]: 105155, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 54f32f7 (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

Change 54f32f7 (ovirt-web-ui) 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-web-ui/commit/54f32f7ae113ddfca97335b147245b… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17589/

1 0

[CQ]: 54f32f7 (ovirt-web-ui) failed "ovirt-4.3" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

Change 54f32f7 (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/54f32f7ae113ddfca97335b147245b… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2621/

1 0

[CQ]: 105020, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 105169, 15 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 103916,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 105168, 15 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

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

04 Dec '19

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

1 0

[CQ]: 104569,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

Change 104569,2 (ovirt-engine) 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/104569/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17578/

1 0

[CQ]: 105351,2 (cockpit-ovirt) failed "ovirt-4.3" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 105042,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Dec '19

04 Dec '19

Change 105042,12 (ovirt-engine) 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/105042/12 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17573/

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 04 Dec '19

04 Dec '19

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

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 04 Dec '19

04 Dec '19

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

1 0

oVirt infra daily report - unstable production jobs - 1028
by jenkins＠jenkins.phx.ovirt.org 04 Dec '19

04 Dec '19

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

1 0

[CQ]: 105319,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

Change 105319,2 (ovirt-engine) 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/105319/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17568/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #1177
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/11…> Changes: ------------------------------------------ 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-fedora-base-fc29-x86_64/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 6cbb066d15a4751af995329e75d0c99f19fa049c (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6cbb066d15a4751af995329e75d0c99f19fa049c Commit message: "usrc: disable pusher functionality if it was not imported" > git rev-list --no-walk 6cbb066d15a4751af995329e75d0c99f19fa049c # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins2349188754050532118.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 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 fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-base-fc29 + 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 fedora-base-fc29 yum + local repo_name=fedora-base-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-base-fc29 /var/www/html/repos/yum/fedora-base-fc29/base + check_yum_sync_needed fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-base-fc29 + 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/fedora-base-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-base-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-base-fc29 ++ 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=fedora-base-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-base-fc29/base --norepopath --newest-only --urls --quiet Error setting up repositories: Cannot retrieve metalink for repository: fedora-base-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #3077
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> Changes: ------------------------------------------ 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-kvm-common-el7-x86_…> 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 6cbb066d15a4751af995329e75d0c99f19fa049c (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6cbb066d15a4751af995329e75d0c99f19fa049c Commit message: "usrc: disable pusher functionality if it was not imported" > git rev-list --no-walk 6cbb066d15a4751af995329e75d0c99f19fa049c # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1068140342502527257.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-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-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=centos-kvm-common-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-kvm-common-el7 yum + local repo_name=centos-kvm-common-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/centos-kvm-common-el7 /var/www/html/repos/yum/centos-kvm-common-el7/base + check_yum_sync_needed centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=centos-kvm-common-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-kvm-common-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=centos-kvm-common-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-kvm-common-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/centos-kvm-common-el7/base --norepopath --newest-only --urls --quiet Error setting up repositories: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml does not exist + reposync_out='Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-29&arch=x86_64 error was File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml.tmp is not XML' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 102769,10 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

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

1 0

[CQ]: 105317, 1 (jenkins) failed "dummy-master" system tests, but isn't the failure root cause
by oVirt Jenkins 03 Dec '19

03 Dec '19

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

1 0

[JIRA] (OVIRT-2845) Jenkins jobs for java-client-kubevirt
by Anton Marchukov (oVirt JIRA) 03 Dec '19

03 Dec '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2845?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2845: ---------------------------------------- [~accountid:557058:7013bb8c-48b2-4b9b-898e-eccf5fb61fad] [~accountid:557058:200ed3d7-7a49-4dd4-b3f4-7359590e646f] merged. Please check once post-merge finishes. > Jenkins jobs for java-client-kubevirt > ------------------------------------- > > Key: OVIRT-2845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2845 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > Hi, > I am working on java-client-kubevirt and have this patch [1] which works > locally. I would like to enable jenkins jobs so I can make sure jenkins is > able to build as well. > Please based the jobs on vdsm-jsonrpc-java project. > Thanks, > Piotr > [1] https://gerrit.ovirt.org/#/c/105207/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JIRA] (OVIRT-2845) Jenkins jobs for java-client-kubevirt
by Martin Perina (oVirt JIRA) 03 Dec '19

03 Dec '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2845?page=com.atlassian.jira.… ] Martin Perina commented on OVIRT-2845: -------------------------------------- Should be solved by merging [https://gerrit.ovirt.org/105317|https://gerrit.ovirt.org/105317] > Jenkins jobs for java-client-kubevirt > ------------------------------------- > > Key: OVIRT-2845 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2845 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > Hi, > I am working on java-client-kubevirt and have this patch [1] which works > locally. I would like to enable jenkins jobs so I can make sure jenkins is > able to build as well. > Please based the jobs on vdsm-jsonrpc-java project. > Thanks, > Piotr > [1] https://gerrit.ovirt.org/#/c/105207/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[CQ]: 104831,8 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

Change 104831,8 (ovirt-engine) 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/104831/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17560/

1 0

[JIRA] (OVIRT-2845) Jenkins jobs for java-client-kubevirt
by Piotr Kliczewski (oVirt JIRA) 03 Dec '19

03 Dec '19

Piotr Kliczewski created OVIRT-2845: --------------------------------------- Summary: Jenkins jobs for java-client-kubevirt Key: OVIRT-2845 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2845 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Piotr Kliczewski Assignee: infra Hi, I am working on java-client-kubevirt and have this patch [1] which works locally. I would like to enable jenkins jobs so I can make sure jenkins is able to build as well. Please based the jobs on vdsm-jsonrpc-java project. Thanks, Piotr [1] https://gerrit.ovirt.org/#/c/105207/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100114)

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

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

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

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

1 0

[CQ]: 102896,8 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

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

1 0

[CQ]: 105257,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

Change 105257,3 (ovirt-imageio) 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/105257/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17550/

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64 #122
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-sclo-rh-release-7.6…> Changes: ------------------------------------------ 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-sclo-rh-release-7.6…> 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 6cbb066d15a4751af995329e75d0c99f19fa049c (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 6cbb066d15a4751af995329e75d0c99f19fa049c Commit message: "usrc: disable pusher functionality if it was not imported" > git rev-list --no-walk 6cbb066d15a4751af995329e75d0c99f19fa049c # timeout=10 [system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2132289302989240617.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 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

1 1

[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 275 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.3-suite-master/275/ Build Number: 275 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #275 [Dominik Holler] network: Give time for the network update to finish ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 006_migrations.migrate_vm_43 Error Message: Fault reason is "Operation Failed". Fault detail is "[Cannot migrate VM because the VM is in Not Responding status.]". HTTP response code is 409. -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> end captured stdout << ---------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test-scenarios/006_migrations.py", line 90, in migrate_vm host=Host(name=dst_host) File "/home/jenkins/agent/workspace/ovirt-system-tests_compat-4.3-suite-master/ovirt-system-tests/compat-4.3-suite-master/test_utils/__init__.py", line 251, in assert_finished_within func(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py", line 31116, in migrate return self._internal_action(action, 'migrate', None, headers, query, wait) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 299, in _internal_action return future.wait() if wait else future File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 55, in wait return self._code(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 296, in callback self._check_fault(response) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 134, in _check_fault self._raise_error(response, body.fault) File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line 118, in _raise_error raise error Fault reason is "Operation Failed". Fault detail is "[Cannot migrate VM because the VM is in Not Responding status.]". HTTP response code is 409. -------------------- >> begin captured stdout << --------------------- source host: lago-compat-4-3-suite-master-host-1 destination host: lago-compat-4-3-suite-master-host-0 --------------------- >> end captured stdout << ----------------------

1 1

[CQ]: 105239,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 03 Dec '19

03 Dec '19

Change 105239,2 (ovirt-engine) 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/105239/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17547/

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

Failed to run project_setup.sh for: #1758 ovirt-imageio [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.

1 0

oVirt infra daily report - unstable production jobs - 1027
by jenkins＠jenkins.phx.ovirt.org 03 Dec '19

03 Dec '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #2166 ovirt-engine [build-artifacts]. 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.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #1738 ovirt-imageio [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 vm0091.workers-phx.ovirt.org.

1 0

[JENKINS] Failed to setup proejct ovirt-imageio_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

Failed to run project_setup.sh for: #1730 ovirt-imageio [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.

1 0

[CQ]: 653b577 (ovirt-ansible-vm-infra) failed "ovirt-master" system tests
by oVirt Jenkins 02 Dec '19

02 Dec '19

Change 653b577 (ovirt-ansible-vm-infra) 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-vm-infra/commit/653b577b898f06362a60… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/17544/

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-engine_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 02 Dec '19

02 Dec '19

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

1 0