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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5437 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-cfmpr.___
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/QTL7KL7VK4QJHI7UD3CTZS7SAXTCJEVQ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5437 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-7khh8.___
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/REKS5BGDXKALJFCVQCI4DC6F64ZTNI43/


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

2019-09-06 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 04e85715491aefb65d2ff2546d1770f9c0028945 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 04e85715491aefb65d2ff2546d1770f9c0028945
Commit message: "global-setup: Fix Python package names on Fedora"
 > git rev-list --no-walk 04e85715491aefb65d2ff2546d1770f9c0028945 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins1438670372806365806.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 nmstate_kubernetes-nmstate_standard-check-pr

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#573 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-skvf5.___
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/DHIBB5J3Q7CUAKECKRFD2B3VKYHMLOOJ/


[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

2019-09-06 Thread Anton Marchukov (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39792#comment-39792
 ] 

Anton Marchukov commented on OVIRT-2794:


Just to clarify that this currently affects manual OST and nightly OST jobs 
(the ones that were switched to containers). 

I see that docker_cleanup.sh handles “ImageNotFoundException”, but in this case 
this is not what docker library throws and we get HTTP 404 error when it works 
through docker API. So we suspect that we now have some incompatibility between 
APIs of the docker library inside the container and the actual docker running 
on the host. Though it might be just a bug in docker client failing to properly 
reraise HTTP exception into the proper one.

Since it fails all manual jobs I have applied a workaround right inside the 
Jenkins job by changing “cleanup_docker || failed=true” to "cleanup_docker || 
failed=false”. It is not committed into git yet as I assume it is just 
temporary workaround. 


> OST is broken since this morning - looks like infra issue
> -
>
> Key: OVIRT-2794
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> The last successful build was today at 08:10:
> Since then all builds fail very early with the error below - which is not
> related to oVirt.
> Removing image:
> sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa,
> force=True
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222,
> in _raise_for_status
> response.raise_for_status()
>   File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True=False
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 349, in 
> main()
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 37, in main
> safe_image_cleanup(client, whitelisted_repos)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 107, in safe_image_cleanup
> _safe_rm(client, parent)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 329, in _safe_rm
> client.images.remove(image_id, force=force)
>   File "/usr/lib/python3.6/site-packages/docker/models/images.py", line
> 288, in remove
> self.client.api.remove_image(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line
> 19, in wrapped
> return f(self, resource_id, *args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in
> remove_image
> return self._result(res, True)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228,
> in _result
> self._raise_for_status(response)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224,
> in _raise_for_status
> raise create_api_error_from_http_exception(e)
>   File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in
> create_api_error_from_http_exception
> raise cls(e, response=response, explanation=explanation)
> docker.errors.NotFound: 404 Client Error: Not Found ("reference does not
> exist")
> Aborting.
> Build step 'Execute shell' marked build as failure
> x
> [image: Failed > Console Output]
> 
> #5542 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5541 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5540 
> Sep 5, 2019 3:01 PM
> 
> [image: Failed > Console Output]
> 
> #5539 
> Sep 5, 2019 2:13 PM
> 

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#575 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-9v8tg.___
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/SJWF2XGSGHUZMECTJU56LH6DDFSC2HPW/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#574 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-m3fm1.___
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/CJOVGE2CHAMF7BRJSAMD2CDUUP5RCSUA/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#575 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-xx7vc.___
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/FMJZMNOLWROBARHFY32XHBFQITXF5DCD/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#574 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-80zv1.___
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/JXNL4IZKIPNM6XUBZ7UYHOFUGOMI65OI/


[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

2019-09-06 Thread Anton Marchukov (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39794#comment-39794
 ] 

Anton Marchukov commented on OVIRT-2794:


[~accountid:557058:cc1e0e66-9881-45e2-b0b7-ccaa3e60f26e] it is actually not 
that new, the solution predates the podman AFAIK. It is just it was partially 
enabled for OST just recently, but before that the solution itself developed 
and existed for other items. The podman should be considered in roadmap for 
supporting next centos version, as we consume docker from the distro.

> OST is broken since this morning - looks like infra issue
> -
>
> Key: OVIRT-2794
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> The last successful build was today at 08:10:
> Since then all builds fail very early with the error below - which is not
> related to oVirt.
> Removing image:
> sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa,
> force=True
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222,
> in _raise_for_status
> response.raise_for_status()
>   File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True=False
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 349, in 
> main()
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 37, in main
> safe_image_cleanup(client, whitelisted_repos)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 107, in safe_image_cleanup
> _safe_rm(client, parent)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 329, in _safe_rm
> client.images.remove(image_id, force=force)
>   File "/usr/lib/python3.6/site-packages/docker/models/images.py", line
> 288, in remove
> self.client.api.remove_image(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line
> 19, in wrapped
> return f(self, resource_id, *args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in
> remove_image
> return self._result(res, True)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228,
> in _result
> self._raise_for_status(response)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224,
> in _raise_for_status
> raise create_api_error_from_http_exception(e)
>   File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in
> create_api_error_from_http_exception
> raise cls(e, response=response, explanation=explanation)
> docker.errors.NotFound: 404 Client Error: Not Found ("reference does not
> exist")
> Aborting.
> Build step 'Execute shell' marked build as failure
> x
> [image: Failed > Console Output]
> 
> #5542 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5541 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5540 
> Sep 5, 2019 3:01 PM
> 
> [image: Failed > Console Output]
> 
> #5539 
> Sep 5, 2019 2:13 PM
> 
> [image: Failed > Console Output]
> 
> #5538 
> Sep 5, 2019 1:58 PM
> 
> [image: Failed > Console Output]
> 
> #5537 

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#576 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-5240m.___
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/FJWTAXNTFLBD7EBXVJPQDZ357HEROH24/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#577 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-9nxsz.___
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/QJMSVV4WGKUT7ZNJJDNS3CXNYQTFEBRM/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#579 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-j1ng3.___
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/YELQXDVPQV5YSUXCTYD7IFQB5DUUYVQC/


[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

2019-09-06 Thread Ryan Barry (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39793#comment-39793
 ] 

Ryan Barry commented on OVIRT-2794:
---

Since this is relatively new, is there any reason we're not using podman
instead of docker?

On Fri, Sep 6, 2019, 15:51 Anton Marchukov (oVirt JIRA) <



> OST is broken since this morning - looks like infra issue
> -
>
> Key: OVIRT-2794
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> The last successful build was today at 08:10:
> Since then all builds fail very early with the error below - which is not
> related to oVirt.
> Removing image:
> sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa,
> force=True
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222,
> in _raise_for_status
> response.raise_for_status()
>   File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True=False
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 349, in 
> main()
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 37, in main
> safe_image_cleanup(client, whitelisted_repos)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 107, in safe_image_cleanup
> _safe_rm(client, parent)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 329, in _safe_rm
> client.images.remove(image_id, force=force)
>   File "/usr/lib/python3.6/site-packages/docker/models/images.py", line
> 288, in remove
> self.client.api.remove_image(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line
> 19, in wrapped
> return f(self, resource_id, *args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in
> remove_image
> return self._result(res, True)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228,
> in _result
> self._raise_for_status(response)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224,
> in _raise_for_status
> raise create_api_error_from_http_exception(e)
>   File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in
> create_api_error_from_http_exception
> raise cls(e, response=response, explanation=explanation)
> docker.errors.NotFound: 404 Client Error: Not Found ("reference does not
> exist")
> Aborting.
> Build step 'Execute shell' marked build as failure
> x
> [image: Failed > Console Output]
> 
> #5542 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5541 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5540 
> Sep 5, 2019 3:01 PM
> 
> [image: Failed > Console Output]
> 
> #5539 
> Sep 5, 2019 2:13 PM
> 
> [image: Failed > Console Output]
> 
> #5538 
> Sep 5, 2019 1:58 PM
> 
> [image: Failed > Console Output]
> 
> #5537 
> Sep 5, 2019 1:50 PM
> 
> [image: Failed > Console Output]
> 

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#578 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-w5nnm.___
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/RSANZ6VFBK36USNRV7VCZ4Z4Q2MZVVGZ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#578 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-pt4st.___
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/XUSDB4BYCYMHHXF7D755JW4D2KRZ747K/


[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

2019-09-06 Thread Ryan Barry (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39795#comment-39795
 ] 

Ryan Barry commented on OVIRT-2794:
---

That's what I mean. podman is also in el7, and if it's already a little
broken (this ticket), why not replace it with something which does not have
these problems?

On Fri, Sep 6, 2019, 15:58 Anton Marchukov (oVirt JIRA) <



> OST is broken since this morning - looks like infra issue
> -
>
> Key: OVIRT-2794
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> The last successful build was today at 08:10:
> Since then all builds fail very early with the error below - which is not
> related to oVirt.
> Removing image:
> sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa,
> force=True
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222,
> in _raise_for_status
> response.raise_for_status()
>   File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True=False
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 349, in 
> main()
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 37, in main
> safe_image_cleanup(client, whitelisted_repos)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 107, in safe_image_cleanup
> _safe_rm(client, parent)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 329, in _safe_rm
> client.images.remove(image_id, force=force)
>   File "/usr/lib/python3.6/site-packages/docker/models/images.py", line
> 288, in remove
> self.client.api.remove_image(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line
> 19, in wrapped
> return f(self, resource_id, *args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in
> remove_image
> return self._result(res, True)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228,
> in _result
> self._raise_for_status(response)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224,
> in _raise_for_status
> raise create_api_error_from_http_exception(e)
>   File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in
> create_api_error_from_http_exception
> raise cls(e, response=response, explanation=explanation)
> docker.errors.NotFound: 404 Client Error: Not Found ("reference does not
> exist")
> Aborting.
> Build step 'Execute shell' marked build as failure
> x
> [image: Failed > Console Output]
> 
> #5542 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5541 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5540 
> Sep 5, 2019 3:01 PM
> 
> [image: Failed > Console Output]
> 
> #5539 
> Sep 5, 2019 2:13 PM
> 
> [image: Failed > Console Output]
> 
> #5538 
> Sep 5, 2019 1:58 PM
> 
> [image: Failed > Console Output]
> 
> #5537 
> Sep 5, 2019 1:50 PM
> 
> [image: Failed 

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#576 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-vfhzw.___
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/FK3GGBDNPRIMDK4Z4QUMD6JXLIHHMRGF/


[JIRA] (OVIRT-2794) OST is broken since this morning - looks like infra issue

2019-09-06 Thread Anton Marchukov (oVirt JIRA)

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=39796#comment-39796
 ] 

Anton Marchukov commented on OVIRT-2794:


[~accountid:557058:cc1e0e66-9881-45e2-b0b7-ccaa3e60f26e] I think before 
replacing anything we need to figure out what is the problem exactly. So for 
this ticket we will certainly just fix the issue as it seems to be related to 
the set of patches we merged last few days.  

Then the solution is a bit more complex than a local box and involves multiple 
hosts and operation systems. E.g. we pretty much do relay on docker serving 
over a socket as a networked service. So replacing will involve some 
reengineering.



> OST is broken since this morning - looks like infra issue
> -
>
> Key: OVIRT-2794
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2794
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Nir Soffer
>Assignee: infra
>
> The last successful build was today at 08:10:
> Since then all builds fail very early with the error below - which is not
> related to oVirt.
> Removing image:
> sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa,
> force=True
> Traceback (most recent call last):
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 222,
> in _raise_for_status
> response.raise_for_status()
>   File "/usr/lib/python3.6/site-packages/requests/models.py", line 893, in
> raise_for_status
> raise HTTPError(http_error_msg, response=self)
> requests.exceptions.HTTPError: 404 Client Error: Not Found for url:
> http+docker://localunixsocket/v1.30/images/sha256:f8e5aa8e979155e074411bfef9adade6cdcdf3a5a2eb1d5ad2dbf0288d585ffa?force=True=False
> During handling of the above exception, another exception occurred:
> Traceback (most recent call last):
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 349, in 
> main()
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 37, in main
> safe_image_cleanup(client, whitelisted_repos)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 107, in safe_image_cleanup
> _safe_rm(client, parent)
>   File
> "/home/jenkins/workspace/ovirt-system-tests_manual/jenkins/scripts/docker_cleanup.py",
> line 329, in _safe_rm
> client.images.remove(image_id, force=force)
>   File "/usr/lib/python3.6/site-packages/docker/models/images.py", line
> 288, in remove
> self.client.api.remove_image(*args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/utils/decorators.py", line
> 19, in wrapped
> return f(self, resource_id, *args, **kwargs)
>   File "/usr/lib/python3.6/site-packages/docker/api/image.py", line 481, in
> remove_image
> return self._result(res, True)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 228,
> in _result
> self._raise_for_status(response)
>   File "/usr/lib/python3.6/site-packages/docker/api/client.py", line 224,
> in _raise_for_status
> raise create_api_error_from_http_exception(e)
>   File "/usr/lib/python3.6/site-packages/docker/errors.py", line 31, in
> create_api_error_from_http_exception
> raise cls(e, response=response, explanation=explanation)
> docker.errors.NotFound: 404 Client Error: Not Found ("reference does not
> exist")
> Aborting.
> Build step 'Execute shell' marked build as failure
> x
> [image: Failed > Console Output]
> 
> #5542 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5541 
> Sep 5, 2019 3:02 PM
> 
> [image: Failed > Console Output]
> 
> #5540 
> Sep 5, 2019 3:01 PM
> 
> [image: Failed > Console Output]
> 
> #5539 
> Sep 5, 2019 2:13 PM
> 
> [image: Failed > Console Output]
> 
> #5538 
> Sep 5, 2019 1:58 PM
> 

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#577 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-jrk6d.___
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/DKV5N6QG525CLSBGYJM5ED7EV4AYAXRV/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#579 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-3dhln.___
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/ATEUEDHLSS3OMVQNAJ2FBBV6LSCMXUDP/


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

2019-09-06 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 04e85715491aefb65d2ff2546d1770f9c0028945 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 04e85715491aefb65d2ff2546d1770f9c0028945
Commit message: "global-setup: Fix Python package names on Fedora"
 > git rev-list --no-walk 04e85715491aefb65d2ff2546d1770f9c0028945 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins6427962739361120086.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 

oVirt infra daily report - unstable production jobs - 940

2019-09-06 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/940//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins
 
 
 
 RHEVM CI Jenkins Daily Report - 06/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_ansible-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_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-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.

   
   
   
  

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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#590 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-1wnn6.___
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/2X55BCW47A5PJI4VKHL2HYTD7TMGVMVC/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#590 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-6qzcw.___
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/3FK3ZWLUP5UQXTBRR53WQDU6UI7S3HHV/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5441 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-vgvw6.___
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/VV7KLDAM5WP2BTF7YUKQI3SKCG6PVUG7/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-4pjg1.___
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/DMATTOHR5O6U7QEYO3DXQKQLCIW4DIBV/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-bw12m.___
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/FTKTSAJ5EDQISG5YAVLEIIHWUSFBSU7I/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-0hqsd.___
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/BFZGDZ6M4T4UXBZBWT2OOFIP63GXQJKP/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-9b084.___
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/NMXPQIEELFM6VU2ZGQS6K7OCBIHNXJKF/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-ksdqf.___
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/AYGJV44DMIIFZD6KPP247UE5MTMZNOQO/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-ktw6j.___
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/HVFCKE4HXH6ABSNEI4SZ5ETNO7WJPKUS/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#9 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-4459t.___
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/4GF357WFSQ6OLMABZRFUT2YJCBJSRVVZ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-2cblt.___
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/CNMTRLQG2RF5AD5PA7WBJB43TF7QNPLC/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-8pstj.___
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/X3FI6MATMOETSJN6I4PXFPDOBCVTIFI7/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-17cg4.___
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/TOLSZWDBJ6RTMQSZP6466BESRAFRN6EE/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5440 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-fzd7f.___
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/V3YVPX5F7QQIGSUS3NPYLBWDDTWRDYBY/


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

2019-09-06 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 04e85715491aefb65d2ff2546d1770f9c0028945 (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 04e85715491aefb65d2ff2546d1770f9c0028945
Commit message: "global-setup: Fix Python package names on Fedora"
 > git rev-list --no-walk 04e85715491aefb65d2ff2546d1770f9c0028945 # timeout=10
[system-sync_mirrors-sac-gluster-ansible-el7-x86_64] $ /bin/bash -xe 
/tmp/jenkins1552577173211918149.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_master_standard-poll-upstream-sources

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-6k10n.___
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/SKJ6PF5X5NS7QHRWOZT6AQ544AWGEQZN/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-x969z.___
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/744ZM6QQJNR7PQ5NX4MHLGQQJ7XKZJVW/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-qllqn.___
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/WROVO5Q263EUSBWZR4VY5RP2Z7MVQLRW/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-77p6n.___
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/OMEKCNLTM37XOQMK77QYSFLEIISVYUKP/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-l1bnv.___
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/3GKIQ7L7N42YOI5UHOKOL3QMOFQ2K5UA/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-4ff1j.___
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/F43OJXJGYGW63KHLMWU4YKSIGBAMCKJK/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#348 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-lx75g.___
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/4DSDMRX2R5TYSLMDIXKU6GTF4LHLEZUK/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#9 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-8xbrc.___
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/WF4ZWAFTURNPQSYXEK53CMWYDKVANW7L/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#9 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-9rj7v.___
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/JILOCC6Y5X7NODUXVB5ZQXT5NH2YYAHY/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#9 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-7636r.___
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/2Y5XXQUM4TBWYOL4AATUBXM6ISJNL2X4/


[oVirt Jenkins] ovirt-system-tests_compat-4.3-suite-master - Build # 186 - Still Failing!

2019-09-06 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/186/
Build Number: 186
Build Status:  Still Failing
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




-
Failed Tests:
-
No tests ran.___
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/2UKBTLVR7ZFFGHBSPRGQAXJSVNIK6RA3/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#573 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-q4ncc.___
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/DTWOR4GFYLFP6WU7KYWHJ4MC2MZ7WV6K/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5439 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-s79jh.___
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/PCGE62JUI4DTOUNKWEMB4SSPRUT4EWQI/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#5438 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-ffhbh.___
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/YGHEUZACRGIOMR74YPFDFF7TLE3V42MY/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#580 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-bx77d.___
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/E3YEKCDFKWGRZK73NTQMFMKBAOJ375CK/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#583 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-xmrx4.___
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/SZAJGPKYWE7MTPUK5NKWBX7RFALB4IRJ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#586 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-djcbv.___
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/OAB4QB2THCGLFXKEUASSHPAFA5VVLG6M/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#587 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-8zm57.___
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/QAOGDPMLD7MASYBAVZGMTEM4FJ2FEXSO/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#587 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-r9m3w.___
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/QSTK7HSFCCYQHPRVZELSU4TIKHNBX35B/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#586 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-g2155.___
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/G63WGU5435ATG2RJGGEOV7BYOIIOZP7G/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#588 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-42lnd.___
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/3MPRH7B4OL4XJR7SZUWXTRLL7KOB756R/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#588 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-49x38.___
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/MVOOHWMOQUL3DHCUNS3EST476PSWXUM6/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#589 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-5l56s.___
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/EZFMGQVQIJ4PFR7Q5FT3SHGHY5IIKG6Z/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#580 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-bc68g.___
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/P7D3U25KG3OKTSLHVSHPJVP722RWC46J/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#583 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-0q80b.___
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/4SWP76U5NM2C3RWO2Z3TJJJDX3JKPZKU/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#585 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-wdbbg.___
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/JLU4V4AF2HX3HN2GTQMH2ETVQYGKRK2S/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#585 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-38152.___
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/XMFFIECVW46D5AWOMNJRVXITRHVXQ2WZ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#582 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-f8nqz.___
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/HSC77D6IKY3Q7QUVNGGWJWRDWO4T3A6T/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#582 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-dkfnr.___
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/J2LGNYOXM5H34C7J4EKB7EYEQ45QK7ZH/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#581 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-740tn.___
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/54DTSUDQSI2V3M4VKOBJCDVSXLOISVZ3/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#581 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-rtxvc.___
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/IB32FK457OF5KVXNW77UPODO4XK45DF7/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#584 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-2wzms.___
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/UXGHIY5HLI4CI4HFBEKE4TTCTIH545QU/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#584 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-1cvdh.___
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/7EFJRSEG5U4OFWDIUW66HTR4XS2UVUSJ/


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

2019-09-06 Thread jenkins
Failed to run project_setup.sh for:
#589 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-5mrb1.___
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/3NIPQZ5KFQVW67VMPJC7ABFKGOPJSB2K/