- Infra - oVirt List Archives

[CQ]: 88440, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Mar '18

04 Mar '18

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

1 0

[CQ]: 88436, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Mar '18

04 Mar '18

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

1 0

[CQ]: 88404,3 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 04 Mar '18

04 Mar '18

Change 88404,3 (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/88404/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1019/

1 0

[JIRA] (OVIRT-1915) Add option to filter packages in OST manual
by Daniel Belenky (oVirt JIRA) 04 Mar '18

04 Mar '18

This is a multi-part message in MIME format... ------------=_1520167130-28938-119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Daniel Belenky created OVIRT-1915: ------------------------------------- Summary: Add option to filter packages in OST manual Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1520167130-28938-119 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Daniel Belenky created OVIRT-1915:</h3> <pre> Summary: Add option to filter packages in OST manual Key: OVIRT-1915 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1915 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Daniel Belenky Assignee: infra</pre> <p>Sometimes we want to filter packages that are being downloaded through repoman. In order to do so, we need to expose repoman's filtering API through Jenkins build parameters.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <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> ------------=_1520167130-28938-119--

1 0

[CQ]: 88261, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Mar '18

04 Mar '18

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

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1328
by jenkins＠jenkins.phx.ovirt.org 03 Mar '18

03 Mar '18

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 ea02d358e4b5ba495ce4f865f48d932427cd0bdb (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ea02d358e4b5ba495ce4f865f48d932427cd0bdb Commit message: "Revert "Install base packeges and start services from global_setup"" > git rev-list --no-walk ea02d358e4b5ba495ce4f865f48d932427cd0bdb # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins164901057006435231.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

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #1252
by jenkins＠jenkins.phx.ovirt.org 03 Mar '18

03 Mar '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/1252/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 ea02d358e4b5ba495ce4f865f48d932427cd0bdb (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ea02d358e4b5ba495ce4f865f48d932427cd0bdb Commit message: "Revert "Install base packeges and start services from global_setup"" > git rev-list --no-walk ea02d358e4b5ba495ce4f865f48d932427cd0bdb # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins8318438236398692928.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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-extras-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

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

02 Mar '18

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

1 0

[CQ]: 88294, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

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

1 0

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

02 Mar '18

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

1 0

[CQ]: 88137, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

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

1 0

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

02 Mar '18

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

1 0

OST Failure - Weekly update [24/02/2018-02/03/2018]
by Dafna Ron 02 Mar '18

02 Mar '18

Hello, I would like to update on this week's failures and OST current status. We had a failed change that caused other changes to fail: 1. Remove use of end_play and fail module - https://gerrit.ovirt.org/#/c/88250/ date: 27-02-2018 version: master/4.2 test failed: 002_bootstrap.verify_add_hosts fix: reverted until it can be fixed: https://gerrit.ovirt.org/#/c/88327/ bug: https://bugzilla.redhat.com/show_bug.cgi?id=1540260 I re-triggered some of the failed changes that were effected by the above change. However, I am still seeing ovirt-engine project is failing in cq so I am expecting some new issues to appear which would be reported next week. *Below you can see the chart for this week's resolved issues but cause of failure: * Code= regression of working components/functionalities Configurations - package related issues Other = failed build artifacts Infra = infrastructure/OST/Lago related issues <https://gerrit.ovirt.org/#/c/88327/> <https://gerrit.ovirt.org/#/c/88327/> <https://gerrit.ovirt.org/#/c/88327/> *Below is a chart of resolved failures based on ovirt version* *Below is a chart showing failures by suite type: * Thank you, Dafna <https://gerrit.ovirt.org/#/c/88327/>

1 0

[CQ]: 85505, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

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

1 0

[CQ]: 88402,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 02 Mar '18

02 Mar '18

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

1 0

[CQ]: 88046, 11 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 02 Mar '18

02 Mar '18

Change 88046,11 (ovirt-hosted-engine-setup) 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/88046/11 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5866/

4 8

[oVirt CI] standard-enqueue - Build #10842 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 02 Mar '18

02 Mar '18

------=_Part_121_1399173834.1520000736197 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/10842/ Build Name: #10842 Build Description: Gerrit: 88128 - ovirt-engine-sdk-java (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/88128 - title: Skip javadoc creation on fc28 - project: ovirt-engine-sdk-java - branch: sdk_3.6 - author: Ondra Machacek <omachace(a)redhat.com> ------=_Part_121_1399173834.1520000736197--

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 02 Mar '18

02 Mar '18

This is a multi-part message in MIME format... ------------=_1519999376-14302-262 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Greg Sheremeta commented on OST-99: ----------------------------------- > I would not start with the container I'm close to having something pretty nice with docker-compose and the docker API via OST :) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1519999376-14302-262 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Greg Sheremeta commented on OST-99:</h3> <blockquote><p>I would not start with the container</p></blockquote> <p>I'm close to having something pretty nice with docker-compose and the docker API via OST :)</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <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> ------------=_1519999376-14302-262--

1 0

[CQ]: 88365, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Mar '18

02 Mar '18

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

1 0

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

02 Mar '18

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 ea02d358e4b5ba495ce4f865f48d932427cd0bdb (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ea02d358e4b5ba495ce4f865f48d932427cd0bdb Commit message: "Revert "Install base packeges and start services from global_setup"" > git rev-list --no-walk ea02d358e4b5ba495ce4f865f48d932427cd0bdb # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1936353913668535630.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

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

02 Mar '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 113 - Failure!
by jenkins＠jenkins.phx.ovirt.org 01 Mar '18

01 Mar '18

------=_Part_99_1852828559.1519872072909 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-= master/=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-ma= ster/113/ Build Number: 113 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #113 [Dominik Holler] network: Add test to check ports on ovirt-provider-ovn [Evgheni Dereveanchin] Remove getbadges.io notifications [Evgheni Dereveanchin] Install base packeges and start services from global= _setup ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 1000_analyze_postgresql.analyze_postgres Error Message: Failed to perform the postgres analysis. Exit code is 1 -------------------- >> begin captured logging << -------------------- lago.plugins.vm: INFO: * Copy /home/jenkins/workspace/ovirt-system-test= s_performance-suite-master/ovirt-system-tests/performance-suite-master/../c= ommon/test-scenarios-files/analyze_postgresql.sh to lago-performance-suite-= master-engine:/root: ?[0m?[0m lago.ssh: DEBUG: start task:6c85fba2-eb7c-4a72-a502-9fe95033e6d1:Get ssh cl= ient for lago-performance-suite-master-engine: lago.ssh: DEBUG: end task:6c85fba2-eb7c-4a72-a502-9fe95033e6d1:Get ssh clie= nt for lago-performance-suite-master-engine: lago.plugins.vm: INFO: * Copy /home/jenkins/workspace/ovirt-system-test= s_performance-suite-master/ovirt-system-tests/performance-suite-master/../c= ommon/test-scenarios-files/analyze_postgresql.sh to lago-performance-suite-= master-engine:/root: ?[32mSuccess?[0m (in 0:00:00) lago.ssh: DEBUG: start task:0c75fae2-c903-417d-9110-3567d549bb1f:Get ssh cl= ient for lago-performance-suite-master-engine: lago.ssh: DEBUG: end task:0c75fae2-c903-417d-9110-3567d549bb1f:Get ssh clie= nt for lago-performance-suite-master-engine: lago.ssh: DEBUG: Running e53ba1ec on lago-performance-suite-master-engine: = bash -ex /root/analyze_postgresql.sh lago.ssh: DEBUG: Command e53ba1ec on lago-performance-suite-master-engine r= eturned with 1 lago.ssh: DEBUG: Command e53ba1ec on lago-performance-suite-master-engine o= utput: Loaded plugins: fastestmirror, versionlock Examining /var/tmp/yum-root-EPVzG6/pgdg-centos95-9.5-3.noarch.rpm: pgdg-cen= tos95-9.5-3.noarch Marking /var/tmp/yum-root-EPVzG6/pgdg-centos95-9.5-3.noarch.rpm to be insta= lled Resolving Dependencies --> Running transaction check ---> Package pgdg-centos95.noarch 0:9.5-3 will be installed --> Finished Dependency Resolution Dependencies Resolved =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Package Arch Version Repository = Size =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Installing: pgdg-centos95 noarch 9.5-3 /pgdg-centos95-9.5-3.noarch 2= .2 k Transaction Summary =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Install 1 Package Total size: 2.2 k Installed size: 2.2 k Downloading packages: Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : pgdg-centos95-9.5-3.noarch = 1/1=20 Verifying : pgdg-centos95-9.5-3.noarch = 1/1=20 Installed: pgdg-centos95.noarch 0:9.5-3 = =20 Complete! Loaded plugins: fastestmirror, versionlock Determining fastest mirrors * base: mirror.den1.denvercolo.net * extras: mirror.chpc.utah.edu * updates: mirror.hmc.edu Resolving Dependencies --> Running transaction check ---> Package pgbadger.noarch 0:9.2-1.rhel7 will be installed ---> Package pgcluu.noarch 0:2.6-1.rhel7 will be installed --> Finished Dependency Resolution Dependencies Resolved =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Package Arch Version Repository = Size =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Installing: pgbadger noarch 9.2-1.rhel7 pgdg95 2= 99 k pgcluu noarch 2.6-1.rhel7 pgdg95 3= 04 k Transaction Summary =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Install 2 Packages Total download size: 603 k Installed size: 2.5 M Downloading packages: ---------------------------------------------------------------------------= ----- Total 342 kB/s | 603 kB 00:01= =20 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : pgbadger-9.2-1.rhel7.noarch = 1/2=20 Installing : pgcluu-2.6-1.rhel7.noarch = 2/2=20 Verifying : pgcluu-2.6-1.rhel7.noarch = 1/2=20 Verifying : pgbadger-9.2-1.rhel7.noarch = 2/2=20 Installed: pgbadger.noarch 0:9.2-1.rhel7 pgcluu.noarch 0:2.6-1.rhel7 = =20 Complete! lago.ssh: DEBUG: Command e53ba1ec on lago-performance-suite-master-engine = errors: + yum install -y https://download.postgresql.org/pub/repos/yum/9.5/redhat/= rhel-7-x86_64/pgdg-centos95-9.5-3.noarch.rpm + yum install -y pgbadger pgcluu + cd /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_log/ ++ su - postgres -c 'scl enable rh-postgresql95 -- psql postgres postgres = -t -c '\''show log_filename'\''' ++ sed 2d + pglog=3D' postgresql-%m.log' ++ date +postgresql-%m.log + pglog=3Dpostgresql-02.log + mkdir pgbadger + pgbadger postgresql-02.log --outdir pgbadger FATAL: logfile "postgresql-02.log" must exist! --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/1000_analyze_po= stgresql.py", line 54, in analyze_postgres ' Exit code is %s' % result.code File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line 29, i= n eq_ raise AssertionError(msg or "%r !=3D %r" % (a, b)) 'Failed to perform the postgres analysis. Exit code is 1\n-----------------= --- >> begin captured logging << --------------------\nlago.plugins.vm: INF= O: * Copy /home/jenkins/workspace/ovirt-system-tests_performance-suite-= master/ovirt-system-tests/performance-suite-master/../common/test-scenarios= -files/analyze_postgresql.sh to lago-performance-suite-master-engine:/root:= \x1b[0m\x1b[0m\nlago.ssh: DEBUG: start task:6c85fba2-eb7c-4a72-a502-9fe950= 33e6d1:Get ssh client for lago-performance-suite-master-engine:\nlago.ssh: = DEBUG: end task:6c85fba2-eb7c-4a72-a502-9fe95033e6d1:Get ssh client for lag= o-performance-suite-master-engine:\nlago.plugins.vm: INFO: * Copy /home= /jenkins/workspace/ovirt-system-tests_performance-suite-master/ovirt-system= -tests/performance-suite-master/../common/test-scenarios-files/analyze_post= gresql.sh to lago-performance-suite-master-engine:/root: \x1b[32mSuccess\x1= b[0m (in 0:00:00)\nlago.ssh: DEBUG: start task:0c75fae2-c903-417d-9110-3567= d549bb1f:Get ssh client for lago-performance-suite-master-engine:\nlago.ssh= : DEBUG: end task:0c75fae2-c903-417d-9110-3567d549bb1f:Get ssh client for l= ago-performance-suite-master-engine:\nlago.ssh: DEBUG: Running e53ba1ec on = lago-performance-suite-master-engine: bash -ex /root/analyze_postgresql.sh\= nlago.ssh: DEBUG: Command e53ba1ec on lago-performance-suite-master-engine = returned with 1\nlago.ssh: DEBUG: Command e53ba1ec on lago-performance-suit= e-master-engine output:\n Loaded plugins: fastestmirror, versionlock\nExami= ning /var/tmp/yum-root-EPVzG6/pgdg-centos95-9.5-3.noarch.rpm: pgdg-centos95= -9.5-3.noarch\nMarking /var/tmp/yum-root-EPVzG6/pgdg-centos95-9.5-3.noarch.= rpm to be installed\nResolving Dependencies\n--> Running transaction check\= n---> Package pgdg-centos95.noarch 0:9.5-3 will be installed\n--> Finished = Dependency Resolution\n\nDependencies Resolved\n\n=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\n Packag= e Arch Version Repository Size\n= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D\nInstalling:\n pgdg-centos95 noarch 9.5-3 /pg= dg-centos95-9.5-3.noarch 2.2 k\n\nTransaction Summary\n=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= \nInstall 1 Package\n\nTotal size: 2.2 k\nInstalled size: 2.2 k\nDownloadi= ng packages:\nRunning transaction check\nRunning transaction test\nTransact= ion test succeeded\nRunning transaction\n Installing : pgdg-centos95-9.5-3= .noarch 1/1 \n Verifying : pgdg-centos9= 5-9.5-3.noarch 1/1 \n\nInstalled:\n pgdg= -centos95.noarch 0:9.5-3 \= n\nComplete!\nLoaded plugins: fastestmirror, versionlock\nDetermining faste= st mirrors\n * base: mirror.den1.denvercolo.net\n * extras: mirror.chpc.uta= h.edu\n * updates: mirror.hmc.edu\nResolving Dependencies\n--> Running tran= saction check\n---> Package pgbadger.noarch 0:9.2-1.rhel7 will be installed= \n---> Package pgcluu.noarch 0:2.6-1.rhel7 will be installed\n--> Finished = Dependency Resolution\n\nDependencies Resolved\n\n=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D\n Packag= e Arch Version Repository Size\n= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D\nInstalling:\n pgbadger noarch 9.2-1.rhel= 7 pgdg95 299 k\n pgcluu noarch 2.6-= 1.rhel7 pgdg95 304 k\n\nTransaction Summary\n=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D\nInstall 2 Packages\n\nTotal download size: 603 k\nInstalled size: = 2.5 M\nDownloading packages:\n---------------------------------------------= -----------------------------------\nTotal = 342 kB/s | 603 kB 00:01 \nRunning transaction check\nRunn= ing transaction test\nTransaction test succeeded\nRunning transaction\n In= stalling : pgbadger-9.2-1.rhel7.noarch 1/2= \n Installing : pgcluu-2.6-1.rhel7.noarch = 2/2 \n Verifying : pgcluu-2.6-1.rhel7.noarch = 1/2 \n Verifying : pgbadger-9.2-1.rhel7.noarch = 2/2 \n\nInstalled:\n pgbadger.noarch 0:9.2-1.rhel7 = pgcluu.noarch 0:2.6-1.rhel7 \n\nComplete!\n\nlago.ssh: DEBUG:= Command e53ba1ec on lago-performance-suite-master-engine errors:\n + yum = install -y https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-7-= x86_64/pgdg-centos95-9.5-3.noarch.rpm\n+ yum install -y pgbadger pgcluu\n+ = cd /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_log/\n++ su - postgres -c = \'scl enable rh-postgresql95 -- psql postgres postgres -t -c \'\\\'\'show = log_filename\'\\\'\'\'\n++ sed 2d\n+ pglog=3D\' postgresql-%m.log\'\n++ dat= e +postgresql-%m.log\n+ pglog=3Dpostgresql-02.log\n+ mkdir pgbadger\n+ pgba= dger postgresql-02.log --outdir pgbadger\nFATAL: logfile "postgresql-02.log= " must exist!\n\n--------------------- >> end captured logging << ---------= ------------' ------=_Part_99_1852828559.1519872072909--

1 1

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

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

[CQ]: 84793, 13 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 84792, 12 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

[CQ]: 82851, 28 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 88292, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

[CQ]: 88318, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 88065, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 87117,1 (ioprocess) failed "ovirt-4.2" system tests
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Yaniv Kaul (oVirt JIRA) 01 Mar '18

01 Mar '18

This is a multi-part message in MIME format... ------------=_1519916823-27449-246 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ] Yaniv Kaul commented on OST-99: ------------------------------- I think it'd be easier to start with running those tests from the Engine VM, though I really like the containers idea - if it works well, we can probably use container for other areas as well (storage !). I would not start with the container just because it'll offset us from our main goal of getting the UI automation in. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OST-99 > URL: https://ovirt-jira.atlassian.net/browse/OST-99 > Project: oVirt system tests > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1519916823-27449-246 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plug… ]</pre> <h3>Yaniv Kaul commented on OST-99:</h3> <p>I think it'd be easier to start with running those tests from the Engine VM, though I really like the containers idea – if it works well, we can probably use container for other areas as well (storage !).</p> <p>I would not start with the container just because it'll offset us from our main goal of getting the UI automation in.</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OST-99 URL: https://ovirt-jira.atlassian.net/browse/OST-99 Project: oVirt system tests Issue Type: Improvement Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <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> ------------=_1519916823-27449-246--

1 0

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

01 Mar '18

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

1 0

[CQ]: 88104, 7 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 88072, 5 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 88063, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[CQ]: 88322, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[JIRA] (OVIRT-1914) jenkins_master_check-patch-fc26-x86_64 failed on cmake = 3.10.1-11.fc26 dep
by Daniel Belenky (oVirt JIRA) 01 Mar '18

01 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1914?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1914: ------------------------------------- Assignee: Daniel Belenky (was: infra) > jenkins_master_check-patch-fc26-x86_64 failed on cmake = 3.10.1-11.fc26 dep > --------------------------------------------------------------------------- > > Key: OVIRT-1914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1914 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Slaves > Reporter: danken > Assignee: Daniel Belenky > > http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2330/co… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[CQ]: 88164, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

[JIRA] (OVIRT-1914) jenkins_master_check-patch-fc26-x86_64 failed on cmake = 3.10.1-11.fc26 dep
by danken (oVirt JIRA) 01 Mar '18

01 Mar '18

This is a multi-part message in MIME format... ------------=_1519907628-13919-231 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit danken created OVIRT-1914: ----------------------------- Summary: jenkins_master_check-patch-fc26-x86_64 failed on cmake = 3.10.1-11.fc26 dep Key: OVIRT-1914 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1914 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Slaves Reporter: danken Assignee: infra http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2330/co… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081) ------------=_1519907628-13919-231 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>danken created OVIRT-1914:</h3> <pre> Summary: jenkins_master_check-patch-fc26-x86_64 failed on cmake = 3.10.1-11.fc26 dep Key: OVIRT-1914 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1914 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Slaves Reporter: danken Assignee: infra</pre> <p><a href="http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2330/co…">http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc26-x86_64/2330/co…</a></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)</p> <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> ------------=_1519907628-13919-231--

1 0

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

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

[CQ]: 87815, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

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

01 Mar '18

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

1 0

[CQ]: 88202, 8 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0

oVirt infra weekly meeting notes 28.02.2018
by Evgheni Dereveanchin 01 Mar '18

01 Mar '18

Hi everyone, Please find the topics of this week's infra meeting below: *PHX DC: - Engine upgraded to 4.2.1- One FC27 slave enabled on Jenkins- Mock updated upstream - need to update snapshots on el7 and all fedoras- Jenkins security advisory - patch prepared- Global_setup patch split for better readability- Bare metal management plugin for several Jenkins instances- Beaker plugin not doing what we need- Foreman plugin exists but unmaintained- scripted slave plugin?AI: - Prepare snapshot update patch* -- Regards, Evgheni Dereveanchin

3 2

[CQ]: 88130, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Mar '18

01 Mar '18

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

1 0