- Infra - oVirt List Archives

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1160
by jenkins＠jenkins.phx.ovirt.org 02 Feb '18

02 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1160/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 4c9ea20c9f09cda53b12f9547e743f8b0d917964 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 4c9ea20c9f09cda53b12f9547e743f8b0d917964 Commit message: "ovirt-vmconsole: re-align" > git rev-list 4c9ea20c9f09cda53b12f9547e743f8b0d917964 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins1122930918533718999.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/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

test failed due to out of free disk space
by Lev Veyde 02 Feb '18

02 Feb '18

Hi, The system test here seems to fail on out of disk space: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests… The error it shows is: ( IOError: [Errno 28] No space left on device ) Can you please take a look? Thanks in advance, -- Lev Veyde Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

[CQ]: 87046, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Feb '18

02 Feb '18

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

1 0

[ OST Failure Report ] [ oVirtMaster (otopi) ] [ 01-02-2018 ] [ 001_initialize_engine.initialize_engine/001_upgrade_engine.test_initialize_engine ]
by Dafna Ron 02 Feb '18

02 Feb '18

Hi, We are failing initialize engine on both basic and upgrade suites. Can you please check? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/86679/ <https://gerrit.ovirt.org/#/c/86679/> - * *core: Check Sequence before/afterLink to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5187/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5187/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5187/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5187/artifact/>(Relevant) error snippet from the log: <error>2018-02-01 10:38:27,057-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Version: otopi-1.7.7_master (otopi-1.7.7-0.0.master.20180201063428.git81ce9b7.el7.centos)2018-02-01 10:38:27,058-0500 ERROR otopi.context context.check:833 "before" parameter of method otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn.Plugin._misc_configure_provider is a string, should probably be a tuple. Perhaps a missing comma?2018-02-01 10:38:27,058-0500 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND methodinfo: {'priority': 5000, 'name': None, 'before': 'osetup.ovn.provider.service.restart', 'after': ('osetup.pki.ca <http://osetup.pki.ca>.available', 'osetup.ovn.services.restart'), 'method': <bound method ?._misc_configure_provider of <otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn.Plugin object at 0x2edf6d0>>, 'condition': <bound method ?.<lambda> of <otopi.plugins.ovirt_engine_setup.ovirt_engine.network.ovirtproviderovn.Plugin object at 0x2edf6d0>>, 'stage': 11}2018-02-01 10:38:27,059-0500 DEBUG otopi.context context._executeMethod:143 method exceptionTraceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/otopi/plugins/otopi/core/misc.py", line 61, in _setup self.context.checkSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 844, in checkSequence raise RuntimeError(_('Found bad "before" or "after" parameters'))RuntimeError: Found bad "before" or "after" parameters2018-02-01 10:38:27,059-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment setup': Found bad "before" or "after" parameters</error>*

2 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1234
by jenkins＠jenkins.phx.ovirt.org 02 Feb '18

02 Feb '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Sandro Bonazzola] ovirt-engine-yarn: re-align [Dafna Ron] ovirt-vmconsole - dropping fc24 [Sandro Bonazzola] ovirt-vmconsole: re-align ------------------------------------------ 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 4c9ea20c9f09cda53b12f9547e743f8b0d917964 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 4c9ea20c9f09cda53b12f9547e743f8b0d917964 Commit message: "ovirt-vmconsole: re-align" > git rev-list 8471ca24bf8f5dbeaff0915ad90fe723bb7db9d4 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins6888143143945093366.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 112, in retrieveAllMD repo._revertOldRepoXML() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1331, in _revertOldRepoXML os.rename(old_data['old_local'], old_data['local']) OSError: [Errno 2] No such file or directory Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 151 - Failure!
by jenkins＠jenkins.phx.ovirt.org 02 Feb '18

02 Feb '18

------=_Part_441_1359819724.1517368692698 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artif… Build Number: 151 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #151 [Sandro Bonazzola] copy-create-job: drop EOLed Fedoras [Dafna Ron] otopi - dropping fc24 [Dafna Ron] ovirt-hosted-engine-setup - dropping fc24 [Daniel Belenky] Mock runner to search full script path [Sandro Bonazzola] otopi: 4.2 and latest fedora [Sandro Bonazzola] ovirt-hosted-engine-setup: 4.2 and new Fedoras [Sandro Bonazzola] ovirt-live: drop project [Daniel Belenky] Introduce Gerrit pipelines [Martin Perina] ovirt-engine-extensions: Add 4.2 jobs for all engine extensions [Dafna Ron] ovirt-release - dropping fc24 [Sandro Bonazzola] ovirt-hosted-engine-setup: re-add fc27 to 4.2 [Sandro Bonazzola] ovirt-release: re-align [Dafna Ron] ovirt-setup-lib - dropping fc24 [Sandro Bonazzola] ovirt-setup-lib: re-align [Dafna Ron] ovirt-iso-uploader - dropping fc24 [Sandro Bonazzola] ovirt-iso-uploader: re-align [Dafna Ron] ovirt-guest-agent - dropping fc24 [Yuval Turgeman] Resolve network issues in kickstart ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_441_1359819724.1517368692698--

1 1

[CQ]: 72018, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Feb '18

02 Feb '18

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

1 0

[CQ]: 61244, 2 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests
by oVirt Jenkins 02 Feb '18

02 Feb '18

Change 61244,2 (ovirt-engine-extension-logger-log4j) 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/61244/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5226/

1 0

[CQ]: 87020, 2 (cockpit-ovirt) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Feb '18

02 Feb '18

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

1 0

[CQ]: 86512, 2 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 02 Feb '18

02 Feb '18

Change 86512,2 (ovirt-engine-nodejs-modules) 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/86512/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5218/

1 0

[CQ]: 87008,1 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86998,1 (ovirt-host-deploy) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 83288, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 83288,1 (ovirt-engine-extension-logger-log4j) 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/83288/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/466/

1 0

[CQ]: 76785,1 (ovirt-engine-yarn) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 76785,1 (ovirt-engine-yarn) 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/76785/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/465/

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Nir Soffer (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-1873: ----------------------------------- I fix the missing ovirt-imageio-common package, see: https://gerrit.ovirt.org/#/c/87034/ But now it fails with mom: nothing provides mom >= 0.5.8 needed by vdsm-4.20.17-29.git89eb77538.fc28.x86_64 We are not ready yet for fcraw. I disabled the job again, will give us more time until jenkins configuration changes. On Thu, Feb 1, 2018 at 6:22 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > We require the package: > > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > > Here are few failing builds, we have more: > > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > > *00:03:25.311* =================================== FAILURES ===================================*00:03:25.311* _________________________ test_import[vdsm.kvm2ovirt] __________________________*00:03:25.312* *00:03:25.312* name = 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def test_import(name):*00:03:25.313* try:*00:03:25.313* > importlib.import_module(name)*00:03:25.313* *00:03:25.313* check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* /usr/lib64/python2.7/importlib/__init__.py:37: in import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.315* *00:03:25.315* from __future__ import absolute_import*00:03:25.315* *00:03:25.315* import argparse*00:03:25.315* from contextlib import contextmanager*00:03:25.315* import itertools*00:03:25.315* import sys*00:03:25.316* import threading*00:03:25.316* *00:03:25.316* > from ovirt_imageio_common import directio*00:03:25.316* E ImportError: No module named ovirt_imageio_common*00:03:25.316* *00:03:25.316* ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== > > > > > Vdsm fcraw builds fail because ovirt-imageio-common is not installed > -------------------------------------------------------------------- > > Key: OVIRT-1873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require the package: > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > Here are few failing builds, we have more: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > *00:03:25.311* =================================== FAILURES > ===================================*00:03:25.311* > _________________________ test_import[vdsm.kvm2ovirt] > __________________________*00:03:25.312* *00:03:25.312* name = > 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* > @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def > test_import(name):*00:03:25.313* try:*00:03:25.313* > > importlib.import_module(name)*00:03:25.313* *00:03:25.313* > check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* > /usr/lib64/python2.7/importlib/__init__.py:37: in > import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ *00:03:25.315* *00:03:25.315* from __future__ import > absolute_import*00:03:25.315* *00:03:25.315* import > argparse*00:03:25.315* from contextlib import > contextmanager*00:03:25.315* import itertools*00:03:25.315* > import sys*00:03:25.316* import threading*00:03:25.316* > *00:03:25.316* > from ovirt_imageio_common import > directio*00:03:25.316* E ImportError: No module named > ovirt_imageio_common*00:03:25.316* *00:03:25.316* > ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 > failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[CQ]: 82649, 2 (ovirt-image-uploader) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 87027,2 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 87027,2 (ovirt-engine) 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/87027/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/463/

1 0

[CQ]: 87036, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 87035, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 87014, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87014,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-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 86910,1 (ovirt-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://gerrit.ovirt.org/#/c/87014/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/458/

1 0

[CQ]: 87013, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87013,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-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 86910,1 (ovirt-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://gerrit.ovirt.org/#/c/87013/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/456/

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Nir Soffer (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-1873: ----------------------------------- With the tested repo, the build fails with: 00:00:40.184 http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fcraw/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found We don't have fcraw, we have fc28: http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc28/ And you can find ovirt-imageio-common there: http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc28/noarch/ovirt-… I think we have several issues: - mismatch for fcraw and fc28 - why not rename fcraw to fc28 - same name used in fedora build system? - the fcraw job was added to the vdsm project before vdsm automation was ready - the fcraw job was disiabled in jenkins - each time jenkins is restarted or upgraded, the job is enabled again, and builds starts to break So we need to: - remove fcraw from vdsm project - prepare vdsm automation for fcraw - enable fcraw when the build is stable > Vdsm fcraw builds fail because ovirt-imageio-common is not installed > -------------------------------------------------------------------- > > Key: OVIRT-1873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require the package: > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > Here are few failing builds, we have more: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > *00:03:25.311* =================================== FAILURES > ===================================*00:03:25.311* > _________________________ test_import[vdsm.kvm2ovirt] > __________________________*00:03:25.312* *00:03:25.312* name = > 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* > @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def > test_import(name):*00:03:25.313* try:*00:03:25.313* > > importlib.import_module(name)*00:03:25.313* *00:03:25.313* > check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* > /usr/lib64/python2.7/importlib/__init__.py:37: in > import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ *00:03:25.315* *00:03:25.315* from __future__ import > absolute_import*00:03:25.315* *00:03:25.315* import > argparse*00:03:25.315* from contextlib import > contextmanager*00:03:25.315* import itertools*00:03:25.315* > import sys*00:03:25.316* import threading*00:03:25.316* > *00:03:25.316* > from ovirt_imageio_common import > directio*00:03:25.316* E ImportError: No module named > ovirt_imageio_common*00:03:25.316* *00:03:25.316* > ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 > failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[CQ]: 87032, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Nir Soffer (oVirt JIRA) 01 Feb '18

01 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-1873: ----------------------------------- The package comes from http://resources.ovirt.org. Looking at vdsm automation: $ for f in automation/check-patch.repos.fc*; do echo $f; cat $f; echo; done automation/check-patch.repos.fc26 tested,http://resources.ovirt.org/repos/ovirt/tested/master/rpm/$distro ovirt-snapshot-static,http://resources.ovirt.org/pub/ovirt-master-snapshot-… ovirt-ci-tools,http://resources.ovirt.org/repos/ci-tools/$distro lago,http://resources.ovirt.org/repos/lago/stable/0.0/rpm/$distro virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$relea… automation/check-patch.repos.fc27 tested,http://resources.ovirt.org/repos/ovirt/tested/master/rpm/$distro virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$relea… automation/check-patch.repos.fcraw virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$relea… Looks like our fcraw repos is wrong. Trying to use the fc27 version... > Vdsm fcraw builds fail because ovirt-imageio-common is not installed > -------------------------------------------------------------------- > > Key: OVIRT-1873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require the package: > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > Here are few failing builds, we have more: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > *00:03:25.311* =================================== FAILURES > ===================================*00:03:25.311* > _________________________ test_import[vdsm.kvm2ovirt] > __________________________*00:03:25.312* *00:03:25.312* name = > 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* > @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def > test_import(name):*00:03:25.313* try:*00:03:25.313* > > importlib.import_module(name)*00:03:25.313* *00:03:25.313* > check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* > /usr/lib64/python2.7/importlib/__init__.py:37: in > import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ *00:03:25.315* *00:03:25.315* from __future__ import > absolute_import*00:03:25.315* *00:03:25.315* import > argparse*00:03:25.315* from contextlib import > contextmanager*00:03:25.315* import itertools*00:03:25.315* > import sys*00:03:25.316* import threading*00:03:25.316* > *00:03:25.316* > from ovirt_imageio_common import > directio*00:03:25.316* E ImportError: No module named > ovirt_imageio_common*00:03:25.316* *00:03:25.316* > ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 > failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[CQ]: 86956, 3 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Barak Korren (oVirt JIRA) 01 Feb '18

01 Feb '18

This is a multi-part message in MIME format... ------------=_1517511446-13753-307 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1873: ------------------------------------- [~nsoffer(a)redhat.com] is there a repo configured where the package would come from? Can you try manually setting up the environment with mock_runner and check if the package is available? > Vdsm fcraw builds fail because ovirt-imageio-common is not installed > -------------------------------------------------------------------- > > Key: OVIRT-1873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > We require the package: > $ grep ovirt-imageio-common automation/check-patch.packages.fcraw > ovirt-imageio-common > Here are few failing builds, we have more: > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… > *00:03:25.311* =================================== FAILURES > ===================================*00:03:25.311* > _________________________ test_import[vdsm.kvm2ovirt] > __________________________*00:03:25.312* *00:03:25.312* name = > 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* > @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def > test_import(name):*00:03:25.313* try:*00:03:25.313* > > importlib.import_module(name)*00:03:25.313* *00:03:25.313* > check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* > /usr/lib64/python2.7/importlib/__init__.py:37: in > import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ *00:03:25.315* *00:03:25.315* from __future__ import > absolute_import*00:03:25.315* *00:03:25.315* import > argparse*00:03:25.315* from contextlib import > contextmanager*00:03:25.315* import itertools*00:03:25.315* > import sys*00:03:25.316* import threading*00:03:25.316* > *00:03:25.316* > from ovirt_imageio_common import > directio*00:03:25.316* E ImportError: No module named > ovirt_imageio_common*00:03:25.316* *00:03:25.316* > ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 > failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) ------------=_1517511446-13753-307 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1873?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1873:</h3> [~nsoffer(a)redhat.com] is there a repo configured where the package would come from? Can you try manually setting up the environment with mock_runner and check if the package is available? <blockquote><h3>Vdsm fcraw builds fail because ovirt-imageio-common is not installed</h3> <pre> Key: OVIRT-1873 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra</pre> We require the package: $ grep ovirt-imageio-common automation/check-patch.packages.fcraw ovirt-imageio-common Here are few failing builds, we have more: <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol…</a> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol…</a> <a href="http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol…">http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol…</a> 00:03:25.311 =================================== FAILURES ===================================*00:03:25.311* _______________________ test_import[vdsm.kvm2ovirt] __________________________*00:03:25.312* 00:03:25.312 name = 'vdsm.kvm2ovirt'*00:03:25.312* 00:03:25.312 @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def test_import(name):*00:03:25.313* try:*00:03:25.313* > <pre>importlib.import_module(name)*00:03:25.313* *00:03:25.313*</pre> check_imports.py:61: 00:03:25.313 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 00:03:25.314 /usr/lib64/python2.7/importlib/__init__.py:37: in import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 00:03:25.315 00:03:25.315 from _future_ import absolute_import*00:03:25.315* 00:03:25.315 import argparse*00:03:25.315* from contextlib import contextmanager*00:03:25.315* import itertools*00:03:25.315* import sys*00:03:25.316* import threading*00:03:25.316* 00:03:25.316 > from ovirt_imageio_common import directio*00:03:25.316* E ImportError: No module named ovirt_imageio_common*00:03:25.316* 00:03:25.316 ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ==========</blockquote> — This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078) <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517511446-13753-307--

1 0

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 77568,2 (ovirt-engine-nodejs) 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/77568/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/449/

1 0

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.1" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 77568,2 (ovirt-engine-nodejs) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/77568/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1562/

1 0

[CQ]: 86512, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 86512,2 (ovirt-engine-nodejs-modules) 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/86512/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/446/

1 0

[CQ]: 83813,1 (ovirt-guest-agent) failed "ovirt-master" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 87010, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 87009, 1 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86996, 1 (ovirt-host-deploy) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86997, 2 (ovirt-host-deploy) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86983, 3 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 82649,2 (ovirt-image-uploader) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 82649,2 (ovirt-image-uploader) 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/82649/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/429/

1 0

[JIRA] (OVIRT-1873) Vdsm fcraw builds fail because ovirt-imageio-common is not installed
by Nir Soffer (oVirt JIRA) 01 Feb '18

01 Feb '18

Nir Soffer created OVIRT-1873: --------------------------------- Summary: Vdsm fcraw builds fail because ovirt-imageio-common is not installed Key: OVIRT-1873 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1873 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra We require the package: $ grep ovirt-imageio-common automation/check-patch.packages.fcraw ovirt-imageio-common Here are few failing builds, we have more: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consol… http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consol… http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consol… *00:03:25.311* =================================== FAILURES ===================================*00:03:25.311* _________________________ test_import[vdsm.kvm2ovirt] __________________________*00:03:25.312* *00:03:25.312* name = 'vdsm.kvm2ovirt'*00:03:25.312* *00:03:25.312* @pytest.mark.parametrize("name", find_modules())*00:03:25.312* def test_import(name):*00:03:25.313* try:*00:03:25.313* > importlib.import_module(name)*00:03:25.313* *00:03:25.313* check_imports.py:61: *00:03:25.313* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.314* /usr/lib64/python2.7/importlib/__init__.py:37: in import_module*00:03:25.314* __import__(name)*00:03:25.314* _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ *00:03:25.315* *00:03:25.315* from __future__ import absolute_import*00:03:25.315* *00:03:25.315* import argparse*00:03:25.315* from contextlib import contextmanager*00:03:25.315* import itertools*00:03:25.315* import sys*00:03:25.316* import threading*00:03:25.316* *00:03:25.316* > from ovirt_imageio_common import directio*00:03:25.316* E ImportError: No module named ovirt_imageio_common*00:03:25.316* *00:03:25.316* ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ========== -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100078)

1 0

[CQ]: 86991,1 (ovirt-host-deploy) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 86991,1 (ovirt-host-deploy) 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/86991/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/426/

1 0

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.1" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 77568,2 (ovirt-engine-nodejs) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/77568/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1560/

1 0

[CQ]: 77568,2 (ovirt-engine-nodejs) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 77568,2 (ovirt-engine-nodejs) 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/77568/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/423/

1 0

[CQ]: 86961, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86959,3 (ovirt-setup-lib) failed "ovirt-4.1" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 81104, 1 (ovirt-engine-wildfly-overlay) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 81104,1 (ovirt-engine-wildfly-overlay) 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/81104/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/420/

1 0

[CQ]: 83813,1 (ovirt-guest-agent) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 83813,1 (ovirt-guest-agent) 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/83813/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/416/

1 0

Change in stdci-staging[master]: dummy change
by review＠gerrit-staging.phx.ovirt.org 01 Feb '18

01 Feb '18

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/128 ) Change subject: dummy change ...................................................................... Patch Set 3: ci re-merge please -- To view, visit https://gerrit-staging.phx.ovirt.org/128 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stdci-staging Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: If619375fc074809adf93dd7305ce472423341b73 Gerrit-Change-Number: 128 Gerrit-PatchSet: 3 Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Thu, 01 Feb 2018 14:36:41 +0000 Gerrit-HasComments: No

1 0

[CQ]: 86985, 2 (otopi) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[CQ]: 86984, 2 (otopi) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Feb '18

01 Feb '18

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

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 01-02-2018 ] [ 002_bootstrap.verify_add_all_hosts ]
by Dafna Ron 01 Feb '18

01 Feb '18

Hi, We failed cq test 002_bootstrap.verify_add_all_hosts for Master vdsm project. Looking at the log, vdsm cannot find master storage domain and engine puts the host on non-operational state. Although on the surface the patch seems to be related, the master storage domain is iscsi whole the patch is related to gluster. I do not think there is a connection between the patch and the failure but can you please have a look to make sure? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/69668/ <https://gerrit.ovirt.org/#/c/69668/> - * *gluster: Fix error when brick is on a btrfs subvolumeLink to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5180/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5180/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5180/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5180/artifact/>(Relevant) error snippet from the log: <error>vdsm: 2018-02-01 03:13:49,211-0500 INFO (jsonrpc/4) [vdsm.api] START createStorageDomain(storageType=3, sdUUID=u'077add35-9171-45d5-b6de-79cc5a853c36', domainName=u'iscsi', typeSpecificArg=u'IdW3HG-K1Af-e0d3-u2O3-rGle-8fk5-ACNk6C', domClass=1, domVersion=u'4', options=None) from=::ffff:192.168.201.4,58530, flow_id=22d4ffd8, task_id=2ce6dd52-3d28-4532-abbf-d78d52af6cda (api:46)2018-02-01 03:14:40,223-0500 INFO (jsonrpc/7) [vdsm.api] START connectStoragePool(spUUID=u'2570c0c9-f872-4e49-964a-ee533a79c3f2', hostID=1, msdUUID=u'077add35-9171-45d5-b6de-79cc5a853c36', masterVersion=1, domainsMap={u'077add35-9171-45d5-b6de-79cc5a853c36': u'active'}, options=None) from=::ffff:192.168.201.4,36310, flow_id=19e9aa89, task_id=878419a0-c5ce-4e35-aed5-b27d56b2886e (api:46)2018-02-01 03:14:40,225-0500 INFO (jsonrpc/7) [storage.StoragePoolMemoryBackend] new storage pool master version 1 and domains map {u'077add35-9171-45d5-b6de-79cc5a853c36': u'Active'} (spbackends:449)2018-02-01 03:14:40,225-0500 INFO (jsonrpc/7) [storage.StoragePool] updating pool 2570c0c9-f872-4e49-964a-ee533a79c3f2 backend from type NoneType instance 0x7f45919e3f20 to type StoragePoolMemoryBackend instance 0x45411b0 (sp:157)2018-02-01 03:14:40,226-0500 INFO (jsonrpc/7) [storage.StoragePool] Connect host #1 to the storage pool 2570c0c9-f872-4e49-964a-ee533a79c3f2 with master domain: 077add35-9171-45d5-b6de-79cc5a853c36 (ver = 1) (sp:692)2018-02-01 03:14:40,462-0500 INFO (jsonrpc/7) [vdsm.api] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=2570c0c9-f872-4e49-964a-ee533a79c3f2, msdUUID=077add35-9171-45d5-b6de-79cc5a853c36' from=::ffff:192.168.201.4,36310, flow_id=19e9aa89, task_id=878419a0-c5ce-4e35-aed5-b27d56b2886e (api:50)2018-02-01 03:14:40,462-0500 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='878419a0-c5ce-4e35-aed5-b27d56b2886e') Unexpected error (task:875)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in connectStoragePool File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1032, in connectStoragePool spUUID, hostID, msdUUID, masterVersion, domainsMap) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1094, in _connectStoragePool res = pool.connect(hostID, msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 704, in connect self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1275, in __rebuild self.setMasterDomain(msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1488, in setMasterDomain raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID)StoragePoolMasterNotFound: Cannot find master domain: u'spUUID=2570c0c9-f872-4e49-964a-ee533a79c3f2, msdUUID=077add35-9171-45d5-b6de-79cc5a853c36'2018-02-01 03:14:40,466-0500 INFO (jsonrpc/7) [storage.TaskManager.Task] (Task='878419a0-c5ce-4e35-aed5-b27d56b2886e') aborting: Task is aborted: "Cannot find master domain: u'spUUID=2570c0c9-f872-4e49-964a-ee533a79c3f2, msdUUID=077add35-9171-45d5-b6de-79cc5a853c36'" - code 304 (task:1181)2018-02-01 03:14:40,467-0500 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=2570c0c9-f872-4e49-964a-ee533a79c3f2, msdUUID=077add35-9171-45d5-b6de-79cc5a853c36' (dispatcher:82)2018-02-01 03:14:40,467-0500 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call StoragePool.connect failed (error 304) in 0.25 seconds (__init__:573)* *engine:* 2018-02-01 03:14:40,603-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [ba52086] EVENT_ID: VDS_SET_NONOPERATIONAL_DOMAIN(522), Host lago-basic-suite-mast er-host-0 cannot access the Storage Domain(s) <UNKNOWN> attached to the Data Center test-dc. Setting Host state to Non-Operational. 2018-02-01 03:14:40,608-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [ba52086] EVENT_ID: VDS_ALERT_FENCE_IS_NOT_CONFIGURED(9,000), Failed to verify Pow er Management configuration for Host lago-basic-suite-master-host-0. 2018-02-01 03:14:40,610-05 WARN [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-70) [ba52086] EVENT_ID: CONNECT_STORAGE_POOL_FAILED(995), Failed to connect Host lago- basic-suite-master-host-0 to Storage Pool test-dc *</error>*

1 0

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 691 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Feb '18

01 Feb '18

------=_Part_445_1158474491.1517409089560 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… Build Number: 691 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #691 [Dafna Ron] ovirt-setup-lib - dropping fc24 [Sandro Bonazzola] ovirt-setup-lib: re-align [Dafna Ron] ovirt-iso-uploader - dropping fc24 [Sandro Bonazzola] ovirt-iso-uploader: re-align [Dafna Ron] ovirt-guest-agent - dropping fc24 [Dafna Ron] ovirt-host-deploy - dropping fc24 [Sandro Bonazzola] ovirt-host-deploy: re-align [Dafna Ron] ovirt-engine-wildfly - dropping fc24 [Sandro Bonazzola] ovirt-engine-wildfly: re-align [Evgheni Dereveanchin] Update mirror snapshot for FC27 to fix gdbm [Dafna Ron] ovirt-engine-wildfly-overlay - dropping fc24 [Yuval Turgeman] appliance-report: try to mount /var ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_445_1158474491.1517409089560--

1 1

[CQ]: 86982,1 (otopi) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Feb '18

01 Feb '18

Change 86982,1 (otopi) 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/86982/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/404/

1 0