Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #161

2019-09-12 Thread jenkins
See 


--
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace 

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 http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision d57e4558406f562560e3e32ece52a98b293cf2a9 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d57e4558406f562560e3e32ece52a98b293cf2a9
Commit message: "staging gate job: use dummy ST project"
 > git rev-list --no-walk d57e4558406f562560e3e32ece52a98b293cf2a9 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins93107486041131412.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror sac-gluster-ansible-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 sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local command=resync_yum_mirror
+ command_args=("${@:2}")
+ local command_args
+ cmd_resync_yum_mirror sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local repo_name=sac-gluster-ansible-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 sac-gluster-ansible-el7 yum
+ local repo_name=sac-gluster-ansible-el7
+ local repo_type=yum
+ sudo install -o jenkins -d /var/www/html/repos/yum 
/var/www/html/repos/yum/sac-gluster-ansible-el7 
/var/www/html/repos/yum/sac-gluster-ansible-el7/base
+ check_yum_sync_needed sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf sync_needed
+ local repo_name=sac-gluster-ansible-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/sac-gluster-ansible-el7
++ IFS=,
++ echo x86_64
+ for arch in '$(IFS=,; echo $repo_archs)'
++ run_reposync sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf --urls --quiet
++ local repo_name=sac-gluster-ansible-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=sac-gluster-ansible-el7 --arch=x86_64 
--cachedir=/home/jenkins/mirrors_cache 
--download_path=/var/www/html/repos/yum/sac-gluster-ansible-el7/base 
--norepopath --newest-only --urls --quiet
+ 
reposync_out='https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905703-gluster-ansible/gluster-ansible-1.0.5-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00861016-gluster-ansible-cluster/gluster-ansible-cluster-1.0.0-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00956485-gluster-ansible-features/gluster-ansible-features-1.0.5-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00942567-gluster-ansible-infra/gluster-ansible-infra-1.0.4-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949988-gluster-ansible-maintenance/gluster-ansible-maintenance-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905778-gluster-ansible-repositories/gluster-ansible-repositories-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949933-gluster-ansible-roles/gluster-ansible-roles-1.0.5-4.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00794582-python-gluster-mgmt-client/python-gluster-mgmt-client-0.2-1.noarch.rpm'
+ [[ -n 

[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#15 vdsm [poll-upstream-sources].
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 openshift-integ-tests-container-92r4t.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W6WANDGU6Q4KXOGHGQ6YWI7T2U7GBSXK/


[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#15 vdsm [poll-upstream-sources].
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 openshift-integ-tests-container-6zxmr.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/NT23M77R5NUUO7OZMYUGK6UUC4W7CL72/


[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#15 vdsm [poll-upstream-sources].
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 openshift-integ-tests-container-1ngrn.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZE4RUDCSI76GZJ22E5RPLKFNVV673TE3/


[JENKINS] Failed to setup proejct vdsm_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#15 vdsm [poll-upstream-sources].
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 openshift-integ-tests-container-24csd.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/OIB36W3ZYIE6XHBXIJ47YNTCTKDSRFF3/


[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 192 - Fixed!

2019-09-12 Thread jenkins
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/192/
Build Number: 192
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #184
[jenkins CI] Auto create ovirt-master

[Ehud Yonasi] Gate: run test suites.

[Barak Korren] gate: Make suit types parameterized


Changes for Build #185
[Galit Rosenthal] Try to fix log collector

[Barak Korren] slave-repos: Update mirror snapshots for EL7

[Barak Korren] Add Zuul jobs & project templates for gating

[Barak Korren] automation: Drop Python 2 packages from FCRAW

[Barak Korren] global-setup: Fix Python package names on Fedora


Changes for Build #186
[jenkins CI] Auto create ovirt-4.3


Changes for Build #187
[jenkins CI] Auto create ovirt-4.3-release


Changes for Build #188
[jenkins CI] Auto create ovirt-master


Changes for Build #189
[jenkins CI] Auto create ovirt-master


Changes for Build #190
[jenkins CI] Auto create ovirt-master


Changes for Build #191
[Martin Perina] ansible: Increase timeout to wait for host to become up


Changes for Build #192
[Roy Golan] master - add java-11-openjdk to repo sync




-
Failed Tests:
-
All tests passed___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/L5VGSHV5WXSGKZF3UZMNJEUURDCZGT2L/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5482 ovirt-system-tests [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 openshift-integ-tests-container-njzjc.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YAU4F5WVKSSZPVTG6W7QMHXEBG2QI565/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5482 ovirt-system-tests [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 openshift-integ-tests-container-q0w2n.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/HFDN7PIP7GTCQSNEDX6VMQX63GHYXJY6/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-5m8wl.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3Y4MM5YACNCWQ5DLRYUHUEY3Z3SEMCW2/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-90x2r.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3H5YDFE6DOMO2V4MWAXIX6W3BLFMSOLN/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-x44n4.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BGWTBDTNKKIPSRJA7LN63AI4OUQ5WGEI/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-r5pvk.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/S4JXBP3LHLP4TXMHYV4F5GIAMVOJIXWM/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-rj2bb.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JYMQC2XYF5JG6EEAVSY4UPEGJLR3QBLP/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-380bg.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YDFQ7FER3DOVSB4AIPOWVAAPOHRC24IM/


[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#355 ovirt-system-tests [poll-upstream-sources].
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 openshift-integ-tests-container-1t9d7.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/NGASSCAXMCZW26NLAXMP2NCWKGY6HE3Y/


oVirt infra daily report - unstable production jobs - 946

2019-09-12 Thread jenkins
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/946//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 12/09/2019
 
00 Unstable Critical
 
   
   changequeue-status_standard-check-patch
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-appliance_4.2_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng-image_4.3_build-artifacts-fc30-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-node-ng-image_master_build-artifacts-fc30-x86_64
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_compat-4.3-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_hc-basic-suite-4.3
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_hc-basic-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-ipv6-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-iscsi-suite-4.3
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-iscsi-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-role-remote-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
   
   ovirt-system-tests_he-basic-suite-master
   
   This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the 
jenkins repo.

   
   
  

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

2019-09-12 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
103291,2 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 102717,6 (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 102717,6 (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/103291/2

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/102717/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15830/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FNCAA46LPXFKXXMP6FUS46WQ7MDHS2YA/


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

2019-09-12 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
102834,6 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 102717,6 (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 102717,6 (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/102834/6

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/102717/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15829/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7ATQSTFEXR4TMTFQSL2YMLQWVCQS333J/


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

2019-09-12 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
103307,1 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 102717,6 (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 102717,6 (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/103307/1

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/102717/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15827/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JGD5S7NJ4GVWEAEGZA5QDSAGIILLE365/


Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #160

2019-09-12 Thread jenkins
See 


--
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace 

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 http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision d57e4558406f562560e3e32ece52a98b293cf2a9 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d57e4558406f562560e3e32ece52a98b293cf2a9
Commit message: "staging gate job: use dummy ST project"
 > git rev-list --no-walk d57e4558406f562560e3e32ece52a98b293cf2a9 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins7300013232942878624.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror sac-gluster-ansible-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 sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local command=resync_yum_mirror
+ command_args=("${@:2}")
+ local command_args
+ cmd_resync_yum_mirror sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local repo_name=sac-gluster-ansible-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 sac-gluster-ansible-el7 yum
+ local repo_name=sac-gluster-ansible-el7
+ local repo_type=yum
+ sudo install -o jenkins -d /var/www/html/repos/yum 
/var/www/html/repos/yum/sac-gluster-ansible-el7 
/var/www/html/repos/yum/sac-gluster-ansible-el7/base
+ check_yum_sync_needed sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf sync_needed
+ local repo_name=sac-gluster-ansible-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/sac-gluster-ansible-el7
++ IFS=,
++ echo x86_64
+ for arch in '$(IFS=,; echo $repo_archs)'
++ run_reposync sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf --urls --quiet
++ local repo_name=sac-gluster-ansible-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=sac-gluster-ansible-el7 --arch=x86_64 
--cachedir=/home/jenkins/mirrors_cache 
--download_path=/var/www/html/repos/yum/sac-gluster-ansible-el7/base 
--norepopath --newest-only --urls --quiet
+ 
reposync_out='https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905703-gluster-ansible/gluster-ansible-1.0.5-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00861016-gluster-ansible-cluster/gluster-ansible-cluster-1.0.0-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00956485-gluster-ansible-features/gluster-ansible-features-1.0.5-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00942567-gluster-ansible-infra/gluster-ansible-infra-1.0.4-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949988-gluster-ansible-maintenance/gluster-ansible-maintenance-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905778-gluster-ansible-repositories/gluster-ansible-repositories-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949933-gluster-ansible-roles/gluster-ansible-roles-1.0.5-4.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00794582-python-gluster-mgmt-client/python-gluster-mgmt-client-0.2-1.noarch.rpm'
+ [[ -n 

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

2019-09-12 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change
103208,3 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 102717,6 (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 102717,6 (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/103208/3

For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/102717/6

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15824/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/2F4EDMNHQWCW6DC4EJMEDIS3UHZLYO5I/


[CQ]: 103294, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests

2019-09-12 Thread oVirt Jenkins
Change 103294,1 (ovirt-engine-api-model) is probably the reason behind recent
system test failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/103294/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15821/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KH4VHWWBIIOLYDIW37VO77OJH46NZHSH/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#621 kubernetes-nmstate [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 openshift-integ-tests-container-q0g72.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YJT6N5FDKHL6GDYUGVGH4HIEJJ3GDND3/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#622 kubernetes-nmstate [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 openshift-integ-tests-container-77ftw.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/76TF3JURGTYCHOWQ32WGXQ5B5RMP7XS4/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#622 kubernetes-nmstate [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 openshift-integ-tests-container-rmdb5.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PQTP5AM2CACP743KX6PMX4ZDHC5Q5SM4/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#620 kubernetes-nmstate [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 openshift-integ-tests-container-zgv73.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZVWCN5WEIX7EGAKMTSVJD4EH4I4SOH3A/


[CQ]: 103293, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests

2019-09-12 Thread oVirt Jenkins
Change 103293,1 (ovirt-engine-api-model) is probably the reason behind recent
system test failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/103293/1

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15819/
___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5ZHDWH56ZKMNULSVG47XME35IBMVESNN/


[JENKINS] Failed to setup proejct standard-manual-runner

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#711 vdsm [check-network].
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 openshift-integ-tests-container-45tvf.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KTQBGOHXOHI4DHWLH4HRPI4PAB35N3TG/


[JENKINS] Failed to setup proejct standard-manual-runner

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#711 vdsm [check-network].
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 openshift-integ-tests-container-qlqp1.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JJEN3XMBYDT27L3SUG4TSZDWB4HW6ROK/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#619 kubernetes-nmstate [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 openshift-integ-tests-container-c31r0.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/6SLXLUGLCH5HXXEAJOJDIEWJFZ4QQUUN/


Build failed in Jenkins: system-sync_mirrors-sac-gluster-ansible-el7-x86_64 #159

2019-09-12 Thread jenkins
See 


--
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace 

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 http://gerrit.ovirt.org/jenkins.git 
 > +refs/heads/*:refs/remotes/origin/* --prune
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision d57e4558406f562560e3e32ece52a98b293cf2a9 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f d57e4558406f562560e3e32ece52a98b293cf2a9
Commit message: "staging gate job: use dummy ST project"
 > git rev-list --no-walk d57e4558406f562560e3e32ece52a98b293cf2a9 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins7514238988619168526.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror sac-gluster-ansible-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 sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local command=resync_yum_mirror
+ command_args=("${@:2}")
+ local command_args
+ cmd_resync_yum_mirror sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf
+ local repo_name=sac-gluster-ansible-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 sac-gluster-ansible-el7 yum
+ local repo_name=sac-gluster-ansible-el7
+ local repo_type=yum
+ sudo install -o jenkins -d /var/www/html/repos/yum 
/var/www/html/repos/yum/sac-gluster-ansible-el7 
/var/www/html/repos/yum/sac-gluster-ansible-el7/base
+ check_yum_sync_needed sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf sync_needed
+ local repo_name=sac-gluster-ansible-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/sac-gluster-ansible-el7
++ IFS=,
++ echo x86_64
+ for arch in '$(IFS=,; echo $repo_archs)'
++ run_reposync sac-gluster-ansible-el7 x86_64 
jenkins/data/mirrors-reposync.conf --urls --quiet
++ local repo_name=sac-gluster-ansible-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=sac-gluster-ansible-el7 --arch=x86_64 
--cachedir=/home/jenkins/mirrors_cache 
--download_path=/var/www/html/repos/yum/sac-gluster-ansible-el7/base 
--norepopath --newest-only --urls --quiet
+ 
reposync_out='https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905703-gluster-ansible/gluster-ansible-1.0.5-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00861016-gluster-ansible-cluster/gluster-ansible-cluster-1.0.0-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00956485-gluster-ansible-features/gluster-ansible-features-1.0.5-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00942567-gluster-ansible-infra/gluster-ansible-infra-1.0.4-3.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949988-gluster-ansible-maintenance/gluster-ansible-maintenance-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00905778-gluster-ansible-repositories/gluster-ansible-repositories-1.0.1-1.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00949933-gluster-ansible-roles/gluster-ansible-roles-1.0.5-4.el7.noarch.rpm
https://copr-be.cloud.fedoraproject.org/results/sac/gluster-ansible/epel-7-x86_64/00794582-python-gluster-mgmt-client/python-gluster-mgmt-client-0.2-1.noarch.rpm'
+ [[ -n 

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5480 ovirt-system-tests [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 openshift-integ-tests-container-k5hc7.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FC527X76Y6SGGGYJF4LMZJY4MOSA2IXD/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#618 kubernetes-nmstate [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 openshift-integ-tests-container-tf4lx.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/3YJTKBF5H46AEG3CS7V4X2JC6OMZMWXM/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#618 kubernetes-nmstate [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 openshift-integ-tests-container-d374n.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7D5KQ7R5AV5QBITSCUS5J3BJ2Y5HWAGX/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#617 kubernetes-nmstate [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 openshift-integ-tests-container-q5xl6.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/WEWZZAWLIFTJY2YY55BWIQUMXXAF5E4L/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#617 kubernetes-nmstate [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 openshift-integ-tests-container-gkblz.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/CCRHERZNS3HHOC7DCV2JOTNXHSDURK47/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5479 ovirt-system-tests [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 openshift-integ-tests-container-5ll1p.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UNYSS4BC7NQGUPSPT5VVZZUI73EOG54R/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#616 kubernetes-nmstate [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 openshift-integ-tests-container-w1d2l.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UHT7JUNEEW3VPQQ7ORYWGLOYONGGJG6D/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#616 kubernetes-nmstate [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 openshift-integ-tests-container-0k72g.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/UCBMLGZZBWGKYEZDTQXEFXRADT4LGMXX/


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

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#3367 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0062.workers-phx.ovirt.org.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/D4PYQO2METONGTEFHXUTPJ5UIA3E4X4C/


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

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#3367 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0006.workers-phx.ovirt.org.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/PR6WCISQNJTVRDNOZKEMUDRAC5PPJ2Q3/


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

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#3367 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0043.workers-phx.ovirt.org.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SS3GCKL5ZUHVCQB4AC6WE5WP6K5BAIL3/


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

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#3367 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0039.workers-phx.ovirt.org.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VDNLOQQESJCSFSQRWTV4K76IUNPE52MF/


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

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#3367 jenkins [check-patch].
It probably means that docker_cleanup.py failed.
This step doesn't fail the job, but we do collect
data about such failures to find the root cause.
Infra owner, ensure that we're not running out of
disk space on vm0219.workers-phx.ovirt.org.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/B433WKHVXVYLKMEFQDO23HJPFVFEIAHI/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#615 kubernetes-nmstate [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 openshift-integ-tests-container-ct0w9.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TCGRZ4VCQS2S4WEPA2Q24VHVJTUEKY6L/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#615 kubernetes-nmstate [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 openshift-integ-tests-container-06w5g.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JQAK2B6FE6KU453GFM5CBZ4WEVPTADCA/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#614 kubernetes-nmstate [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 openshift-integ-tests-container-nrj6v.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7RKND33ROOGMGC3MYBRCE4B33VPHMXGV/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#614 kubernetes-nmstate [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 openshift-integ-tests-container-qr85h.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/7MW6QQ2LP5RZIUQHVFHQKK37TIIXOLNZ/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#613 kubernetes-nmstate [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 openshift-integ-tests-container-1s8v4.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/NVCTCIKEU2P7K46BGCB5JKKVUBU5DOVO/


[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#613 kubernetes-nmstate [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 openshift-integ-tests-container-ztrzr.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/BX5W4KOV64BLGKYFRUH7S3WVWQPI7UY5/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-bxc22.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/77Z35OGEQ2YMAI5TDCXPOMVAGUAM3QNY/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-4lp7c.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/VN4LPFEXY2LJMR65SNLIWQBNZ23FOVCU/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-p4k7k.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/FHDQUAB2SBFXMD2MYKYFIWQPXCB45JLR/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-ww33b.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/ZAQO5R6MN6KCGK7JI3DLPYNMKUX5ZPDD/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-2lsxh.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/W22QI6OZ5AFD4YFMY5AYUWBZP7MW272D/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-74zjq.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/5V6L4UVGWR75N6CQPLSV66NK2T5BZSPS/


[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch

2019-09-12 Thread jenkins
Failed to run project_setup.sh for:
#5478 ovirt-system-tests [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 openshift-integ-tests-container-57rk2.___
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/infra@ovirt.org/message/KSSWQ43NQ7JAC5BFJNZFKBQYFI7XBABV/