- Infra - oVirt List Archives

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

15 Jan '19

Failed to run project_setup.sh for: #1676 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0041.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1671 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0048.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1678 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0049.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1675 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0012.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1680 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0037.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1666 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0047.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1684 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0015.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1666 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0045.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1674 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0040.workers-phx.ovirt.org.

1 0

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

15 Jan '19

Failed to run project_setup.sh for: #1667 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0034.workers-phx.ovirt.org.

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #196
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-x86_64…> Changes: [Barak Korren] master_deploy: Created master deployment flow ------------------------------------------ Started by timer [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-fc29-x86_64…> > 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 d6878e25de65be74c1d9620f4b9e9d8b7cdd9b4e (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f d6878e25de65be74c1d9620f4b9e9d8b7cdd9b4e Commit message: "master_deploy: Created master deployment flow" > git rev-list --no-walk 0a6f56dafee29c0b2970ff3af7a015c7d7b3b973 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins3254171803000921942.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs fedora-updates-fc29 yum + local repo_name=fedora-updates-fc29 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/fedora-updates-fc29 /var/www/html/repos/yum/fedora-updates-fc29/base + check_yum_sync_needed fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=fedora-updates-fc29 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/fedora-updates-fc29 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync fedora-updates-fc29 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=fedora-updates-fc29 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=fedora-updates-fc29 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/fedora-updates-fc29/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, 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 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 897, in _getMetalink raise Errors.RepoError, msg yum.Errors.RepoError: Cannot retrieve metalink for repository: fedora-updates-fc29. Please verify its path and try again + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Liora Milbaum (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Liora Milbaum updated OVIRT-2641: --------------------------------- Status: To Do (was: In Progress) > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Liora Milbaum (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Liora Milbaum commented on OVIRT-2641: -------------------------------------- [~eedri] It is not urgent at all > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '19

Failed to run project_setup.sh for: #3164 kubevirt [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-kubevirt-org-84fqk.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '19

Failed to run project_setup.sh for: #3164 kubevirt [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-kubevirt-org-69l0z.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '19

Failed to run project_setup.sh for: #3161 kubevirt [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-kubevirt-org-sxgfd.

1 0

[CQ]: 3b16711 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 15 Jan '19

15 Jan '19

A system test invoked by the "ovirt-master" change queue including change 3b16711 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 860f6a6 (ovirt-ansible- hosted-engine-setup) 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 860f6a6 (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/3b1671157… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12337/

2 1

[JIRA] (OVIRT-2650) ovirt-master and 4.2 failing on ovirt-ansible-hosted-engine-setup
by Dafna Ron (oVirt JIRA) 15 Jan '19

15 Jan '19

Dafna Ron created OVIRT-2650: -------------------------------- Summary: ovirt-master and 4.2 failing on ovirt-ansible-hosted-engine-setup Key: OVIRT-2650 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest running tests / upgrade-from-release-suite.el7.x86_64 / 001_upgrade_engine.test_initialize_engine patch reported as failed by CQ: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/3b1671157… issue was reported to list {noformat} [ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190114152238-gb5e9p.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190114152253-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed ('FATAL Internal error (main): Please update the Setup packages',) lago.ssh: DEBUG: Command 22b4983a on lago-upgrade-from-release-suite-master-engine errors: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute self.context.runSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation exec('raise info[1], None, info[2]') File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 410, in _customization raise RuntimeError(_('Please update the Setup packages')) RuntimeError: Please update the Setup packages {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Eyal Edri (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2641: ---------------------------------- How urgent is this really is? I prefer to reduce priority if the mirror ends up fixing itself. > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Liora Milbaum (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Liora Milbaum reopened OVIRT-2641: ---------------------------------- > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Liora Milbaum (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Liora Milbaum updated OVIRT-2641: --------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '19

Failed to run project_setup.sh for: #3159 kubevirt [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-kubevirt-org-5f98w.

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2649: ------------------------------------- looking at the job logs linked above: {code} 12:17:48 Filesystem Size Used Avail Use% Mounted on 12:17:48 /dev/vda3 36G 24G 13G 66% / 12:17:48 devtmpfs 6.1G 0 6.1G 0% /dev 12:17:48 tmpfs 6.1G 329M 5.8G 6% /dev/shm 12:17:48 tmpfs 6.1G 828K 6.1G 1% /run 12:17:48 tmpfs 6.1G 0 6.1G 0% /sys/fs/cgroup 12:17:48 /dev/vda1 253M 152M 102M 60% /boot 12:17:48 tmpfs 1.3G 0 1.3G 0% /run/user/1012 12:17:48 tmpfs 1.3G 0 1.3G 0% /run/user/0 12:17:48 ############################################################### 12:17:48 # Slave cleanup done: SUCCESS # 12:17:48 ############################################################### {code} We had 13G available on the salve when we started - how much space do we need exactly? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2649: ------------------------------------- We can probably make {{slave_cleanup.sh}} take more drastic steps if space on the slave goes below a certain threshold. But we need to know what that threshold is. > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:11 AM: -------------------------------------------------------------- I'm not sure bigger disk space is the right solution, we'll just run out again - we need some details before reaching such a decision: # How much space is needed to build appliance and node? # How much space we have on the slaves right now? # What else is taking up space? was (Author: bkorren(a)redhat.com) I'm not sure bigger disk space is the right solution, we'll just run out again - we need some details before reaching such a decision: # How much space is needed to buil,appliance? # How much space we have on the slaves right now? # What else is taking up space? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2649: ------------------------------------- I'm not sure bigger disk space is the right solution, we'll just run out again - we need some details before reaching such a decision: # How much space is needed to buil,appliance? # How much space we have on the slaves right now? # What else is taking up space? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Eyal Edri (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2649: ---------------------------------- the slave got offline automatically due to out of space. Since this only happens on appliance and node build jobs I suggest to create new big VMs for now with more space and assign the appliance and node build jobs to run only them ( we could also run them on Bare metal since its running nightly ) So I suggest to update the jobs to run on bare-metals as a temp WA ( since they run once a day ) and create new VMs with bigger disk space for future. [~dron] can you help with that? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:07 AM: -------------------------------------------------------------- we usually want {{/var/cache}} to stick around since we need the caches to work... but maybe not all of them, I suspect we may have an issue with cleaning unused mock environments. was (Author: bkorren(a)redhat.com) we usually waht {{/var/cache}} to stick around since we nee the caches to work... but maybe no all of them, I suspect we may have an issue with cleaning unused mock environments. > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2649 at 1/15/19 8:07 AM: -------------------------------------------------------------- we usually waht {{/var/cache}} to stick around since we nee the caches to work... but maybe no all of them, I suspect we may have an issue with cleaning unused mock environments. was (Author: bkorren(a)redhat.com) we ususal;y waht {{/var/cache}} to stick around since we nee the caches to work... but maybe no all of them, I suspect we may have an issue with cleaning unused mock environments. > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2649: ------------------------------------- we ususal;y waht {{/var/cache}} to stick around since we nee the caches to work... but maybe no all of them, I suspect we may have an issue with cleaning unused mock environments. > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Eyal Edri (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2649: ---------------------------------- Looking at slave_cleanup.sh we are removing /var/tmp but it doesn't seem to be working well? [~sbonazzo(a)redhat.com]how big are those files usually? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by Eyal Edri (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2649?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2649: ---------------------------------- [~ederevea] [~bkorren(a)redhat.com] [~dron] I see /var is mostly taking up space, with cache and tmp folder taking up the most of it. Are we cleaning it during slave cleanup? > Not enough space on slaves for building > --------------------------------------- > > Key: OVIRT-2649 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Some slave have not enough space for building ovirt-engine appliance > Example: > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:53:22.207* pigz: abort: write error on <stdout> (No space left on > device) > https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… > *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org > <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> > (libvirt el7 phx nested) > *00:50:49.368* pigz: abort: write error on <stdout> (No space left on > device) > Please ensure slaves have enough space. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2649) Not enough space on slaves for building
by sbonazzo (oVirt JIRA) 15 Jan '19

15 Jan '19

sbonazzo created OVIRT-2649: ------------------------------- Summary: Not enough space on slaves for building Key: OVIRT-2649 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2649 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Some slave have not enough space for building ovirt-engine appliance Example: https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… *00:00:00.309* Building remotely on vm0092.workers-phx.ovirt.org <https://jenkins.ovirt.org/computer/vm0092.workers-phx.ovirt.org> (libvirt el7 phx nested) *00:53:22.207* pigz: abort: write error on <stdout> (No space left on device) https://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-fc2… *00:00:00.558* Building remotely on vm0095.workers-phx.ovirt.org <https://jenkins.ovirt.org/computer/vm0095.workers-phx.ovirt.org> (libvirt el7 phx nested) *00:50:49.368* pigz: abort: write error on <stdout> (No space left on device) Please ensure slaves have enough space. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-1922) support 'ci re-merge please' command for github
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1922?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1922: ------------------------------------- This ticket is a request, by [~dron], that needs it.... The current workaround is to go to the webhook invocation history in GitHub, find the right invocation (can be hard for busy projects), and re-send it. > support 'ci re-merge please' command for github > ------------------------------------------------ > > Key: OVIRT-1922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Dafna Ron > Assignee: infra > > As discussed in OVIRT-1919 we do yet support ci re-merge please in github and it would be helpful to add it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-2641 at 1/15/19 6:49 AM: -------------------------------------------------------------- its a simple shell script - any CentOS VM or container can be used as a dev environment for this, you just need yum, yum-utils and distribution-gpg-keys. if you feel like writing orderly STDCI configuration for this and some bats tests, be my guest... was (Author: bkorren(a)redhat.com) its a simple shell script - any CentOS VM or container can be used as a dev environment for this, you just need yum, yum-utils and distribution-gpg-keys. > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

[JIRA] (OVIRT-2641) mirror_mgr.sh - Build error
by Barak Korren (oVirt JIRA) 15 Jan '19

15 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2641?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2641: ------------------------------------- its a simple shell script - any CentOS VM or container can be used as a dev environment for this, you just need yum, yum-utils and distribution-gpg-keys. > mirror_mgr.sh - Build error > --------------------------- > > Key: OVIRT-2641 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2641 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI Mirrors > Reporter: Liora Milbaum > Assignee: infra > > From job run: > [https://jenkins.ovirt.org/blue/organizations/jenkins/system-sync_mirrors-ep…] > {code}+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf > Checking if mirror needs a resync > Traceback (most recent call last): > File "/usr/bin/reposync", line 343, in <module> > main() > File "/usr/bin/reposync", line 175, 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 1465, in _commonLoadRepoXML > local = self.cachedir + '/repomd.xml' > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> > cachedir = property(lambda self: self._dirGetAttr('cachedir')) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr > self.dirSetup() > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup > self._dirSetupMkdir_p(dir) > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p > raise Errors.RepoError, msg > yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100097)

1 0

oVirt infra daily report - unstable production jobs - 705
by jenkins＠jenkins.phx.ovirt.org 15 Jan '19

15 Jan '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/705//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 3b16711 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '19

14 Jan '19

A system test invoked by the "ovirt-4.2" change queue including change 3b16711 (ovirt-ansible-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 860f6a6 (ovirt-ansible-hosted- engine-setup) 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 860f6a6 (ovirt-ansible-hosted- engine-setup) 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/3b1671157… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3718/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Failed to run project_setup.sh for: #3149 kubevirt [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-kubevirt-org-7lkzr.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Failed to run project_setup.sh for: #3147 kubevirt [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-kubevirt-org-vtrb0.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Failed to run project_setup.sh for: #3147 kubevirt [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-kubevirt-org-59jms.

1 0

[CQ]: 860f6a6 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jan '19

14 Jan '19

Change 860f6a6 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3715/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Failed to run project_setup.sh for: #3144 kubevirt [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-kubevirt-org-hg7xb.

1 0

[CQ]: 860f6a6 (ovirt-ansible-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '19

14 Jan '19

Change 860f6a6 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12331/

1 0

[CQ]: 860f6a6 (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.2" system tests
by oVirt Jenkins 14 Jan '19

14 Jan '19

Change 860f6a6 (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Failed to run project_setup.sh for: #3138 kubevirt [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-kubevirt-org-p86jq.

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 452 - Failure!
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/452/ Build Number: 452 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #452 [Dafna Ron] ovirt-master: adding missing packages to reposync ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 704
by jenkins＠jenkins.phx.ovirt.org 14 Jan '19

14 Jan '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/704//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 96611,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Jan '19

13 Jan '19

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

1 0

Fwd: ** PROBLEM Service Alert: jenkins/jenkins.phx.ovirt.org /var/lib/data disk is WARNING **
by Eyal Edri 13 Jan '19

13 Jan '19

Can we check why do we have a spike in usage? maybe due to keeping 14 days of history for all builds? ---------- Forwarded message --------- From: <nagios(a)monitoring.ovirt.org> Date: Sun, Jan 13, 2019 at 4:12 PM Subject: ** PROBLEM Service Alert: jenkins/jenkins.phx.ovirt.org /var/lib/data disk is WARNING ** To: <eedri(a)redhat.com> ***** Nagios ***** Notification Type: PROBLEM Service: jenkins.phx.ovirt.org /var/lib/data disk Host: jenkins Address: 66.187.230.92 State: WARNING Date/Time: Sun Jan 13 14:12:27 UTC 2019 Additional Info: DISK WARNING - free space: /var/lib/data 199785 MB (12.92% inode=99%): -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0