November 2018 - Infra - oVirt List Archives

[CQ]: 95563, 3 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Nov '18

24 Nov '18

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

1 0

[CQ]: 95596, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Nov '18

24 Nov '18

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

1 0

[CQ]: 95595,1 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 24 Nov '18

24 Nov '18

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

1 0

oVirt infra daily report - unstable production jobs - 653
by jenkins＠jenkins.phx.ovirt.org 24 Nov '18

24 Nov '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/653//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 6aa7858 (ovirt-ansible-infra) failed "ovirt-master" system tests
by oVirt Jenkins 23 Nov '18

23 Nov '18

Change 6aa7858 (ovirt-ansible-infra) 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-infra/commit/6aa78585cacc8adb0d33d54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11351/

1 0

[CQ]: 95586, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Nov '18

23 Nov '18

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

1 0

[CQ]: 95383,2 (ovirt-lldp-labeler) failed "ovirt-4.2" system tests
by oVirt Jenkins 23 Nov '18

23 Nov '18

Change 95383,2 (ovirt-lldp-labeler) 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://gerrit.ovirt.org/#/c/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3523/

2 1

[Ovirt] [CQ weekly status] [23-11-2018]
by Dafna Ron 23 Nov '18

23 Nov '18

Hi, This mail is to provide the *current *status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. CQ ovirt-4.2 - YELLOW (#1) e CQ ovirt-Master - RED (#1) - *Project failing* - ovirt-engine - *First job reported*: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267 - *root cause*: https://gerrit.ovirt.org/#/c/95169/ ansible: Remove duplication of vnc_tls option - *Revert for change*: https://gerrit.ovirt.org/95666 - Tomasz Baranski is working on testing and fixing the change. There is a long queue of changes waiting to be tested and the revert patch is in queue. Once revert is tested the jobs for ovirt-engine, unless any other regressions were introduced, project should start to pass. Happy week! Dafna ------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-kvm-common-el7-x86_64 #1933
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ 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-kvm-common-el7-x86_…> > 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 31f05cf869f635237eda123c071e91ba51a2a3e6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 31f05cf869f635237eda123c071e91ba51a2a3e6 Commit message: "Drop mzamazal from basic-suite-master compatibility testing" > git rev-list --no-walk 31f05cf869f635237eda123c071e91ba51a2a3e6 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1363929668501834874.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 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 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

[CQ]: 95025, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Nov '18

23 Nov '18

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

1 0