- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[CQ]: 103293, 1 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 12 Sep '19

12 Sep '19

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/

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 1

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct jenkins_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct nmstate_kubernetes-nmstate_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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-zq47z.

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[CQ]: 103266,3 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_master_standard-poll-upstream-sources
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

oVirt infra daily report - unstable production jobs - 945
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

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

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc30-x86_64 #374
by jenkins＠jenkins.phx.ovirt.org 12 Sep '19

12 Sep '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc30-x86_64…> ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc30-x86_64…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress 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-fedora-updates-fc30-x86_64] $ /bin/bash -xe /tmp/jenkins5628770139268432605.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc30 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc30 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc30 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc30 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc30 yum + local repo_name=fedora-updates-fc30 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc30 /var/www/html/repos/yum/fedora-updates-fc30/base + check_yum_sync_needed fedora-updates-fc30 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc30 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc30 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc30 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc30 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc30 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc30/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1482, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1259, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1025, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 703, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 698, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 635, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 881, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 824, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 921, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 900, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc30. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 102912, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 11 Sep '19

11 Sep '19

A system test invoked by the "ovirt-master" change queue including change 102912,16 (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/102912/16 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/15806/

1 0

[JIRA] (OVIRT-2795) Re: [ovirt-devel] ovirt-vmconsole package issues
by Nir Soffer (oVirt JIRA) 11 Sep '19

11 Sep '19

Nir Soffer created OVIRT-2795: --------------------------------- Summary: Re: [ovirt-devel] ovirt-vmconsole package issues Key: OVIRT-2795 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2795 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra On Wed, Sep 11, 2019 at 4:38 PM Michal Skrivanek < michal.skrivanek(a)redhat.com> wrote: > > > On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > Hi, > > we get a lot of failures in the CI for el7 and fc29 regarding this package > since this morning, i.e. for fc29: > > > in which CI? > Here are some examples: https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa… Adding infra-support to file a bug. > > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > > Can someone take a look at this? > > as it looks like incomplete package or webserver issue it’s best to report > this to infra > > Thanks, Marcin > > > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)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/GE3G2RZ3TPXHV… > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109)

1 0

Re: [ovirt-devel] ovirt-vmconsole package issues
by Michal Skrivanek 11 Sep '19

11 Sep '19

> On 11 Sep 2019, at 11:19, Marcin Sobczyk <msobczyk(a)redhat.com> wrote: > > Hi, > > we get a lot of failures in the CI for el7 and fc29 regarding this package since this morning, i.e. for fc29: in which CI? > > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [MIRROR] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: Interrupted by header callback: Server reports Content-Length: 38712 but expected size is: 38804 > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] [FAILED] ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: No more mirrors to try - All mirrors were already tried without success > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Error: Error downloading packages: > <https://jenkins.ovirt.org/blue/organizations/jenkins/vdsm_standard-check-pa…>[2019-09-11T07:55:42.107Z] Cannot download noarch/ovirt-vmconsole-1.0.7-3.fc29.noarch.rpm: All mirrors were tried > Can someone take a look at this? > > as it looks like incomplete package or webserver issue it’s best to report this to infra > Thanks, Marcin >

2 1

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

11 Sep '19

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

1 0

[JENKINS] Failed to setup proejct ovirt-system-tests_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

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

1 1

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

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

1 0

[JENKINS] Failed to setup proejct standard-manual-runner
by jenkins＠jenkins.phx.ovirt.org 11 Sep '19

11 Sep '19

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

1 0