December 2018 - Infra - oVirt List Archives

ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Nir Soffer 31 Dec '18

31 Dec '18

Started 2 days 11 hr ago Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-…

4 3

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2638: --------------------------------------- The node where the build was running on ( vm0038.workers-phx.ovirt.org ) ran out of disk space. That's why we see all those issues. I'm checking what fills the disk. > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-fc28-x86_64 - Build # 172 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Build Number: 172 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #172 [Yuval Turgeman] build: change root fs to be a logical volume ----------------- Failed Tests: ----------------- No tests ran.

1 1

[oVirt Jenkins] ovirt-node-ng-image_4.3_build-artifacts-el7-x86_64 - Build # 41 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-el7-x8… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-el7-x8… Build Number: 41 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #41 [Sandro Bonazzola] automation: add devices for qemu performances ----------------- Failed Tests: ----------------- No tests ran.

1 1

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #2185
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/2185/displ…> ------------------------------------------ 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-epel-el6-x86_64/ws/> > 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 ebb5016d852a395b97686551537a621133628cd0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ebb5016d852a395b97686551537a621133628cd0 Commit message: "OST: Remove he-basic-ansible master job" > git rev-list --no-walk ebb5016d852a395b97686551537a621133628cd0 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins4301188763427119265.sh + 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' Build step 'Execute shell' marked build as failure

1 2

oVirt infra daily report - unstable production jobs - 690
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

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/690//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Eyal Edri (oVirt JIRA) 30 Dec '18

30 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2638: ---------------------------------- On Sun, Dec 30, 2018, 21:25 Yuval Turgeman <yturgema(a)redhat.com wrote: > Looks like livemedia-creator installed the VM correctly, but failed to > build the final image file for some reason (disk issues?). Stdci failed > the job on timeout, but probably can't kill the hanging process. Is it > possible to take a look at the slave somehow ? > sure, though you will need someone from the CI team to ssh in, if you don't have access to infra servers. > On Sun, Dec 30, 2018, 19:57 Nir Soffer <nsoffer(a)redhat.com wrote: > >> Started 2 days 11 hr ago >> Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or >> <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> >> >> >> https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… >> >> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-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/devel@ovirt.org/message/FXGWNLV3ZLZSN… >> > _______________________________________________ > 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/46JUANKQHKPK7… > > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Yuval Turgeman (oVirt JIRA) 30 Dec '18

30 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-2638: --------------------------------------- Looks like livemedia-creator installed the VM correctly, but failed to build the final image file for some reason (disk issues?). Stdci failed the job on timeout, but probably can't kill the hanging process. Is it possible to take a look at the slave somehow ? On Sun, Dec 30, 2018, 19:57 Nir Soffer <nsoffer(a)redhat.com wrote: > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > > > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… > > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-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/devel@ovirt.org/message/FXGWNLV3ZLZSN… > > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[CQ]: 95496,27 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 30 Dec '18

30 Dec '18

Change 95496,27 (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/95496/27 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12182/

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Eyal Edri (oVirt JIRA) 30 Dec '18

30 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2638: ---------------------------------- Barak, Do we have a timeout for normal STD CI jobs? or its just for OST? On Sun, Dec 30, 2018, 19:48 Nir Soffer (oVirt JIRA) < > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0