- Infra - oVirt List Archives

[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) 14 Jan '19

14 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) 14 Jan '19

14 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) 14 Jan '19

14 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) 14 Jan '19

14 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) 14 Jan '19

14 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) 14 Jan '19

14 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 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/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