July 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-2765) Jenkins builds not running "All nodes of label ‘loader-container’ are offline"
by Barak Korren (oVirt JIRA) 29 Jul '19

29 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2765?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2765: ------------------------------------- For some reason the port jenkins is usign to talk to the containers was closed - I updated the jenkins configuration to re-open it and now we can see working containers again. [~ederevea] do we know why the port was closed all of a sudden? > Jenkins builds not running "All nodes of label ‘loader-container’ are offline" > ------------------------------------------------------------------------------ > > Key: OVIRT-2765 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2765 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Scott Dickerson > Assignee: infra > > Builds for at least ovirt-engine-ui-extensions [1] and > ovirt-engine-nodejs-modules [2] are blocked with an erorr like, "All nodes > of label ‘loader-container’ are offline". Looks like they're all broken > [3]. > Please help! > [1] > https://jenkins.ovirt.org/job/ovirt-engine-ui-extensions_standard-check-pat… > [2] > https://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_standard-check-pa… > [3] https://jenkins.ovirt.org/label/loader-container/ > -- > Scott Dickerson > Senior Software Engineer > RHV-M Engineering - UX Team > Red Hat, Inc -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100106)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #2696
by jenkins＠jenkins.phx.ovirt.org 29 Jul '19

29 Jul '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/59/95959/1:test --prune > git rev-parse origin/test^{commit} # timeout=10 > git rev-parse test^{commit} # timeout=10 Checking out Revision 05b40dfb4ec43a82530e8c471395d1858e5c59e1 (test) > git config core.sparsecheckout # timeout=10 > git checkout -f 05b40dfb4ec43a82530e8c471395d1858e5c59e1 Commit message: "mirror-reposync: remove gluster-3.10 mirror" > git rev-list --no-walk 05b40dfb4ec43a82530e8c471395d1858e5c59e1 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1892789279831032913.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 373, in <module> main() File "/usr/bin/reposync", line 185, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1468, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 777, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 760, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 738, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 715, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2765) Jenkins builds not running "All nodes of label ‘loader-container’ are offline"
by Scott Dickerson (oVirt JIRA) 29 Jul '19

29 Jul '19

Scott Dickerson created OVIRT-2765: -------------------------------------- Summary: Jenkins builds not running "All nodes of label ‘loader-container’ are offline" Key: OVIRT-2765 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2765 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Scott Dickerson Assignee: infra Builds for at least ovirt-engine-ui-extensions [1] and ovirt-engine-nodejs-modules [2] are blocked with an erorr like, "All nodes of label ‘loader-container’ are offline". Looks like they're all broken [3]. Please help! [1] https://jenkins.ovirt.org/job/ovirt-engine-ui-extensions_standard-check-pat… [2] https://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_standard-check-pa… [3] https://jenkins.ovirt.org/label/loader-container/ -- Scott Dickerson Senior Software Engineer RHV-M Engineering - UX Team Red Hat, Inc -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100106)

1 0

[CQ]: 102123, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jul '19

29 Jul '19

A system test invoked by the "ovirt-master" change queue including change 102123,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102089,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102089,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102123/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102089/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15182/

1 0

[CQ]: 102208,3 (ovirt-imageio) failed "ovirt-4.3" system tests
by oVirt Jenkins 29 Jul '19

29 Jul '19

Change 102208,3 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/102208/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1592/

1 0

[CQ]: 102137, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jul '19

29 Jul '19

A system test invoked by the "ovirt-master" change queue including change 102137,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102089,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102089,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102137/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102089/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15177/

1 0

[CQ]: 101866, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jul '19

29 Jul '19

A system test invoked by the "ovirt-master" change queue including change 101866,8 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102089,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102089,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101866/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102089/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15173/

1 0

[CQ]: 102204, 3 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Jul '19

29 Jul '19

A system test invoked by the "ovirt-4.3" change queue including change 102204,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101840,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101840,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/102204/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101840/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1589/

1 0

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

29 Jul '19

A system test invoked by the "ovirt-master" change queue including change 100397,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 102089,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 102089,4 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/100397/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/102089/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15169/

1 0

oVirt infra daily report - unstable production jobs - 900
by jenkins＠jenkins.phx.ovirt.org 29 Jul '19

29 Jul '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/900//artifact/exported-a… Cheers, Jenkins

1 0