- Infra - oVirt List Archives

[JIRA] (OVIRT-1820) ioporcess build-artifacts fails on fedora/ppc64le
by Nir Soffer (oVirt JIRA) 27 Dec '17

27 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1820?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-1820: ----------------------------------- I posted this for removing the fedora/ppc64le jobs: https://gerrit.ovirt.org/#/c/85786/ On Wed, Dec 27, 2017 at 10:20 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. > > I merge a patch today, and build-artifacts fail: > > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… > > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… > > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… > > So it seems that we cannot support fedora on ppc64le now, and we > need to remove these jobs. > > Nir > > ioporcess build-artifacts fails on fedora/ppc64le > ------------------------------------------------- > > Key: OVIRT-1820 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1820 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. > I merge a patch today, and build-artifacts fail: > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… > http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… > So it seems that we cannot support fedora on ppc64le now, and we > need to remove these jobs. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1820) ioporcess build-artifacts fails on fedora/ppc64le
by Nir Soffer (oVirt JIRA) 27 Dec '17

27 Dec '17

Nir Soffer created OVIRT-1820: --------------------------------- Summary: ioporcess build-artifacts fails on fedora/ppc64le Key: OVIRT-1820 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1820 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra We added recently build-artifacts jobs for ioprocess on fedora/ppc64le. I merge a patch today, and build-artifacts fail: http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc26-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fc27-ppc64le/… http://jenkins.ovirt.org/job/ioprocess_master_build-artifacts-fcraw-ppc64le… So it seems that we cannot support fedora on ppc64le now, and we need to remove these jobs. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 85754,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Dec '17

27 Dec '17

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

1 0

[JIRA] (OVIRT-1819) Hanging processes left after mock_runner is being terminated
by Daniel Belenky (oVirt JIRA) 27 Dec '17

27 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1819?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1819: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Hanging processes left after mock_runner is being terminated > ------------------------------------------------------------ > > Key: OVIRT-1819 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1819 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > Priority: Highest > > Since mock_runner.sh runs as $user and mock runs as root, mock_runner can't propagate signals to mock process. > Due to the said above, if mock_runner is being terminated, the mock process will be left behind as an orphaned. > Another symptom is subprocesses of user script which are not being killed after users script returns. > We need to trap signals from mock_runner and implement a message pipe between mock_runner and mock to propagate the signals. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1819) Hanging processes left after mock_runner is being terminated
by Daniel Belenky (oVirt JIRA) 27 Dec '17

27 Dec '17

Daniel Belenky created OVIRT-1819: ------------------------------------- Summary: Hanging processes left after mock_runner is being terminated Key: OVIRT-1819 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1819 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Priority: Highest Since mock_runner.sh runs as $user and mock runs as root, mock_runner can't propagate signals to mock process. Due to the said above, if mock_runner is being terminated, the mock process will be left behind as an orphaned. Another symptom is subprocesses of user script which are not being killed after users script returns. We need to trap signals from mock_runner and implement a message pipe between mock_runner and mock to propagate the signals. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[CQ]: 68408,12 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 27 Dec '17

27 Dec '17

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

1 0

[CQ]: 85734, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Dec '17

27 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85734,1 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 85645,2 (ovirt-provider-ovn) 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 85645,2 (ovirt-provider-ovn) 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/85734/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85645/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4539/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1118
by jenkins＠jenkins.phx.ovirt.org 27 Dec '17

27 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-centos-updates-el7-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 e6220a204f13e53150867224f62e4752cad89cd0 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e6220a204f13e53150867224f62e4752cad89cd0 Commit message: "ioprocess: Exclude fc2* ppc64le tests" > git rev-list e6220a204f13e53150867224f62e4752cad89cd0 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins2742489996658194381.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7/gen' Build step 'Execute shell' marked build as failure

1 1

Change in stage-stdci1[master]: Another patch for checking automerge
by review＠gerrit-staging.phx.ovirt.org 26 Dec '17

26 Dec '17

>From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/112 to look at the new patch set (#2). Change subject: Another patch for checking automerge ...................................................................... Another patch for checking automerge Patch owner would be bkorren Change-Id: I725721eb11285f0566804b92e3a3a6d05ed59cc1 automerge: yes --- M dummy.txt 1 file changed, 2 insertions(+), 0 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/12/112/2 -- To view, visit https://gerrit-staging.phx.ovirt.org/112 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: I725721eb11285f0566804b92e3a3a6d05ed59cc1 Gerrit-Change-Number: 112 Gerrit-PatchSet: 2 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1116
by jenkins＠jenkins.phx.ovirt.org 26 Dec '17

26 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ 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-centos-updates-el7-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 ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 Commit message: "add network suite to manaul job suite selector" > git rev-list ae13ffe0e6eaa8969e7af7741bc7ecb7ca88b739 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3621825039595573999.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 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 1