- Infra - oVirt List Archives

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

24 Nov '18

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

1 0

[CQ]: 7f89654 (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 24 Nov '18

24 Nov '18

Change 7f89654 (ovirt-ansible-v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-v2v-conversion-host/commit/7f89654b9… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11404/

1 0

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

24 Nov '18

Change 6aa7858 (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-infra/commit/6aa78585cacc8adb0d33d54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11398/

1 0

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

24 Nov '18

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

1 0

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

24 Nov '18

Change 95589,4 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95589/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11386/

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fc29-x86_64 #40
by jenkins＠jenkins.phx.ovirt.org 24 Nov '18

24 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fc29-x86_64/40…> ------------------------------------------ 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-fedora-base-fc29-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 97f2a4684a8cee04e4893c1dc32864891f42121d (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 97f2a4684a8cee04e4893c1dc32864891f42121d Commit message: "ovirt-appliance: add builds for 4.3 branch" > git rev-list --no-walk 97f2a4684a8cee04e4893c1dc32864891f42121d # timeout=10 [system-sync_mirrors-fedora-base-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins6609588569099903756.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fc29 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-kvm-common-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-kvm-common-el7' Build step 'Execute shell' marked build as failure

1 1

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

24 Nov '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 374 - Failure!
by jenkins＠jenkins.phx.ovirt.org 24 Nov '18

24 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/374/ Build Number: 374 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #374 [Gal Ben Haim] oc-on-ovirt: Update Orb version to 4.2.7 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 008_basic_ui_sanity.initialize_firefox_42 Error Message: Message: Error forwarding the new session cannot find : Capabilities {acceptInsecureCerts: true, browserName: firefox, marionette: true, platform: LINUX, version: 58.0.1} Stacktrace: at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117) at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84) at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68) at javax.servlet.http.HttpServlet.service (HttpServlet.java:707) at javax.servlet.http.HttpServlet.service (HttpServlet.java:790) at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860) at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168) at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473) at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166) at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155) at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141) at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132) at org.seleniumhq.jetty9.server.Server.handle (Server.java:530) at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347) at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256) at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279) at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102) at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131) at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626) at java.lang.Thread.run (Thread.java:748) -------------------- >> begin captured stdout << --------------------- _init_browser, connecting to hub at http://172.18.0.2:4444/wd/hub Message: Error forwarding the new session cannot find : Capabilities {acceptInsecureCerts: true, browserName: firefox, marionette: true, platform: LINUX, version: 58.0.1} Stacktrace: at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117) at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84) at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68) at javax.servlet.http.HttpServlet.service (HttpServlet.java:707) at javax.servlet.http.HttpServlet.service (HttpServlet.java:790) at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860) at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188) at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168) at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473) at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564) at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166) at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155) at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141) at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132) at org.seleniumhq.jetty9.server.Server.handle (Server.java:530) at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347) at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256) at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279) at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102) at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140) at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131) at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708) at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626) at java.lang.Thread.run (Thread.java:748) WebDriverException in _init_browser connecting to hub --------------------- >> end captured stdout << ---------------------- -------------------- >> begin captured logging << -------------------- selenium.webdriver.remote.remote_connection: DEBUG: POST http://172.18.0.2:4444/wd/hub/session {"capabilities": {"alwaysMatch": {"acceptInsecureCerts": true, "browserName": "firefox", "platformName": "linux", "browserVersion": "58.0.1"}, "firstMatch": [{}]}, "desiredCapabilities": {"acceptInsecureCerts": true, "platform": "LINUX", "browserName": "firefox", "version": "58.0.1", "marionette": true}} urllib3.connectionpool: DEBUG: Starting new HTTP connection (1): 172.18.0.2:4444 urllib3.connectionpool: DEBUG: http://172.18.0.2:4444 "POST /wd/hub/session HTTP/1.1" 500 7909 selenium.webdriver.remote.remote_connection: DEBUG: Finished Request --------------------- >> 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 runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/008_basic_ui_sanity.py", line 219, in initialize_firefox _init_driver(_get_firefox_capabilities()) File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/008_basic_ui_sanity.py", line 239, in _init_driver raise e 'Message: Error forwarding the new session cannot find : Capabilities {acceptInsecureCerts: true, browserName: firefox, marionette: true, platform: LINUX, version: 58.0.1}\nStacktrace:\n at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117)\n at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84)\n at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:707)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:790)\n at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141)\n at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132)\n at org.seleniumhq.jetty9.server.Server.handle (Server.java:530)\n at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347)\n at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256)\n at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279)\n at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102)\n at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131)\n at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626)\n at java.lang.Thread.run (Thread.java:748)\n-------------------- >> begin captured stdout << ---------------------\n_init_browser, connecting to hub at http://172.18.0.2:4444/wd/hub\nMessage: Error forwarding the new session cannot find : Capabilities {acceptInsecureCerts: true, browserName: firefox, marionette: true, platform: LINUX, version: 58.0.1}\nStacktrace:\n at org.openqa.grid.web.servlet.handler.RequestHandler.process (RequestHandler.java:117)\n at org.openqa.grid.web.servlet.DriverServlet.process (DriverServlet.java:84)\n at org.openqa.grid.web.servlet.DriverServlet.doPost (DriverServlet.java:68)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:707)\n at javax.servlet.http.HttpServlet.service (HttpServlet.java:790)\n at org.seleniumhq.jetty9.servlet.ServletHolder.handle (ServletHolder.java:860)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doHandle (ServletHandler.java:535)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doHandle (SessionHandler.java:1595)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextHandle (ScopedHandler.java:188)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doHandle (ContextHandler.java:1253)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:168)\n at org.seleniumhq.jetty9.servlet.ServletHandler.doScope (ServletHandler.java:473)\n at org.seleniumhq.jetty9.server.session.SessionHandler.doScope (SessionHandler.java:1564)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.nextScope (ScopedHandler.java:166)\n at org.seleniumhq.jetty9.server.handler.ContextHandler.doScope (ContextHandler.java:1155)\n at org.seleniumhq.jetty9.server.handler.ScopedHandler.handle (ScopedHandler.java:141)\n at org.seleniumhq.jetty9.server.handler.HandlerWrapper.handle (HandlerWrapper.java:132)\n at org.seleniumhq.jetty9.server.Server.handle (Server.java:530)\n at org.seleniumhq.jetty9.server.HttpChannel.handle (HttpChannel.java:347)\n at org.seleniumhq.jetty9.server.HttpConnection.onFillable (HttpConnection.java:256)\n at org.seleniumhq.jetty9.io.AbstractConnection$ReadCallback.succeeded (AbstractConnection.java:279)\n at org.seleniumhq.jetty9.io.FillInterest.fillable (FillInterest.java:102)\n at org.seleniumhq.jetty9.io.ChannelEndPoint$2.run (ChannelEndPoint.java:124)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.doProduce (EatWhatYouKill.java:247)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.produce (EatWhatYouKill.java:140)\n at org.seleniumhq.jetty9.util.thread.strategy.EatWhatYouKill.run (EatWhatYouKill.java:131)\n at org.seleniumhq.jetty9.util.thread.ReservedThreadExecutor$ReservedThread.run (ReservedThreadExecutor.java:382)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool.runJob (QueuedThreadPool.java:708)\n at org.seleniumhq.jetty9.util.thread.QueuedThreadPool$2.run (QueuedThreadPool.java:626)\n at java.lang.Thread.run (Thread.java:748)\nWebDriverException in _init_browser connecting to hub\n\n--------------------- >> end captured stdout << ----------------------\n-------------------- >> begin captured logging << --------------------\nselenium.webdriver.remote.remote_connection: DEBUG: POST http://172.18.0.2:4444/wd/hub/session {"capabilities": {"alwaysMatch": {"acceptInsecureCerts": true, "browserName": "firefox", "platformName": "linux", "browserVersion": "58.0.1"}, "firstMatch": [{}]}, "desiredCapabilities": {"acceptInsecureCerts": true, "platform": "LINUX", "browserName": "firefox", "version": "58.0.1", "marionette": true}}\nurllib3.connectionpool: DEBUG: Starting new HTTP connection (1): 172.18.0.2:4444\nurllib3.connectionpool: DEBUG: http://172.18.0.2:4444 "POST /wd/hub/session HTTP/1.1" 500 7909\nselenium.webdriver.remote.remote_connection: DEBUG: Finished Request\n--------------------- >> end captured logging << ---------------------'

1 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #2162
by jenkins＠jenkins.phx.ovirt.org 24 Nov '18

24 Nov '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 97f2a4684a8cee04e4893c1dc32864891f42121d (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 97f2a4684a8cee04e4893c1dc32864891f42121d Commit message: "ovirt-appliance: add builds for 4.3 branch" > git rev-list --no-walk 97f2a4684a8cee04e4893c1dc32864891f42121d # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins553410145460668176.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

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

24 Nov '18

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

1 0

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

24 Nov '18

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

1 0

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

24 Nov '18

Change 95595,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95595/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11357/

1 0

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

24 Nov '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/653//artifact/exported-a… Cheers, Jenkins

1 0

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

23 Nov '18

Change 6aa7858 (ovirt-ansible-infra) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://github.com/oVirt/ovirt-ansible-infra/commit/6aa78585cacc8adb0d33d54… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11351/

1 0

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

23 Nov '18

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

1 0

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

23 Nov '18

Change 95383,2 (ovirt-lldp-labeler) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3523/

2 1

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

23 Nov '18

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

1 0

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

23 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-kvm-common-el7-x86_…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 31f05cf869f635237eda123c071e91ba51a2a3e6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 31f05cf869f635237eda123c071e91ba51a2a3e6 Commit message: "Drop mzamazal from basic-suite-master compatibility testing" > git rev-list --no-walk 31f05cf869f635237eda123c071e91ba51a2a3e6 # timeout=10 [system-sync_mirrors-centos-kvm-common-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1363929668501834874.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-kvm-common-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1479, in _commonLoadRepoXML result = self._getFileRepoXML(local, text) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1256, in _getFileRepoXML size=102400) # setting max size as 100K File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1022, in _getFile result = self.grab.urlgrab(misc.to_utf8(relative), local, File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 700, in <lambda> grab = property(lambda self: self._getgrab()) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 695, in _getgrab self._setupGrab() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 632, in _setupGrab urls = self.urls File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 878, in <lambda> urls = property(fget=lambda self: self._geturls(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 875, in _geturls self._baseurlSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 821, in _baseurlSetup mirrorurls.extend(list(self.metalink_data.urls())) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 918, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 914, in _getMetalink self._metalink = metalink.MetaLinkRepoMD(self.metalink_filename) File "/usr/lib/python2.7/site-packages/yum/metalink.py", line 189, in __init__ raise MetaLinkRepoErrorParseFail, "File %s is not XML" % filename yum.metalink.MetaLinkRepoErrorParseFail: File /home/jenkins/mirrors_cache/fedora-base-fc29/metalink.xml is not XML Build step 'Execute shell' marked build as failure

1 1

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

23 Nov '18

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

1 0

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

23 Nov '18

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

1 0

[JIRA] (OVIRT-2587) missing workspace releng-tools on vm0004.workers-phx.ovirt.org
by Dafna Ron (oVirt JIRA) 23 Nov '18

23 Nov '18

Dafna Ron created OVIRT-2587: -------------------------------- Summary: missing workspace releng-tools on vm0004.workers-phx.ovirt.org Key: OVIRT-2587 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2587 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we had a failed check patch due to workspace disappear or not existing on the vm https://jenkins.ovirt.org/blue/organizations/jenkins/releng-tools_standard-… logging this for Evgheni to make sure there is nothing that is deleting workspace mid build. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

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

23 Nov '18

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2601 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv05.phx.ovirt.org-container-3.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2601 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv05.phx.ovirt.org-container-5.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2601 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv05.phx.ovirt.org-container-1.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2600 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv06.infra-phx.ovirt.org-container-7.

1 0

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

23 Nov '18

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

1 0

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

23 Nov '18

Change 95383,2 (ovirt-lldp-labeler) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3521/

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2599 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-zmv17.

1 0

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

23 Nov '18

Change 95383,2 (ovirt-lldp-labeler) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/95383/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3520/

1 0

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

23 Nov '18

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

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #2074
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/2074/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 31f05cf869f635237eda123c071e91ba51a2a3e6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 31f05cf869f635237eda123c071e91ba51a2a3e6 Commit message: "Drop mzamazal from basic-suite-master compatibility testing" > git rev-list --no-walk 31f05cf869f635237eda123c071e91ba51a2a3e6 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins4448743819578125948.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 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

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

23 Nov '18

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

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2596 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-pd6rd.

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Anton Marchukov (oVirt JIRA) 23 Nov '18

23 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2586: ---------------------------------------- Hello All. I have restarted the jenkins. I guess we need to investigate what to do as we are quite a large jenkins shop and there is certainly a limit on how well it can scale. Since infra-support is added, the ticket is already created. Anton. On 23 November 2018 at 10:09:29, Sandro Bonazzola (sbonazzo(a)redhat.com) wrote: > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > > -- > > SANDRO BONAZZOLA > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/25QXLHAYU4XJV… > > Jenkins terribly slow and unresponsive > -------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Jenkins terribly slow and unresponsive
by Sandro Bonazzola 23 Nov '18

23 Nov '18

Hi, jenkins is terribly slow and becoming worse every day. I tried to gain some speed by adding 4 cores to the VM through engine-phx. It's a bit better but the real issue doesn't seem related to CPU power. Can anybody investigate? -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 1

[oVirt CI] standard-enqueue - Build #17584 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/17584/ Build Name: #17584 Build Description: Gerrit: 95484 - ovirt-engine (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/95484 - title: core: Replace usage of older versions in OvfManagerTest - project: ovirt-engine - branch: master - author: Martin Peřina <mperina(a)redhat.com>

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by sbonazzo (oVirt JIRA) 23 Nov '18

23 Nov '18

sbonazzo created OVIRT-2586: ------------------------------- Summary: Jenkins terribly slow and unresponsive Key: OVIRT-2586 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, jenkins is terribly slow and becoming worse every day. I tried to gain some speed by adding 4 cores to the VM through engine-phx. It's a bit better but the real issue doesn't seem related to CPU power. Can anybody investigate? -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engone) ] [ 21-11-2018 ] [ check_update_host ]
by Dafna Ron 23 Nov '18

23 Nov '18

Hi, We have a failure in ovirt-master in basic suite for test check_update_host. Link and headline of suspected patches: ansible: Remove duplication of vnc_tls option - https://gerrit.ovirt.org/#/c/95169/ Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267 Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267/artifa… (Relevant) error snippet from the log: <error> [dron@dron post-002_bootstrap.py]$ egrep 89d99b74-fa6c-4d1d-a261-fb7ca7fcada2 lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log 2018-11-21 13:41:34,209-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 9ms 2018-11-21 13:41:34,224-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckCommand] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckCommand internal: false. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN 2018-11-21 13:41:34,259-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 13ms 2018-11-21 13:41:34,273-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckInternalCommand internal: true. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDS 2018-11-21 13:41:34,277-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 4ms 2018-11-21 13:41:34,281-05 DEBUG [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Inventory hosts: [lago-basic-suite-master-host-0] 2018-11-21 13:41:34,282-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook, --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory2326258642232337463, /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null] 2018-11-21 13:41:37,610-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Ansible playbook command has exited with value: 2 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to run check-update of host 'lago-basic-suite-master-host-0'. 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to check if updates are available for host 'lago-basic-suite-master-host-0' with error message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.' 2018-11-21 13:41:37,616-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates on host lago-basic-suite-master-host-0 with message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.'. [dron@dron post-002_bootstrap.py]$ </error>

5 9

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc29-x86_64 #35
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc29-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-fedora-updates-fc29-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 31f05cf869f635237eda123c071e91ba51a2a3e6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 31f05cf869f635237eda123c071e91ba51a2a3e6 Commit message: "Drop mzamazal from basic-suite-master compatibility testing" > git rev-list --no-walk 31f05cf869f635237eda123c071e91ba51a2a3e6 # timeout=10 [system-sync_mirrors-fedora-updates-fc29-x86_64] $ /bin/bash -xe /tmp/jenkins2735800501484899901.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-updates-fc29 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 1487, in _commonLoadRepoXML self._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

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Nov '18

23 Nov '18

Failed to run project_setup.sh for: #2593 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv05.phx.ovirt.org-container-4.

1 0

[JIRA] (OVIRT-2585) Jenkins web is not responsive
by Edward Haas (oVirt JIRA) 23 Nov '18

23 Nov '18

Edward Haas created OVIRT-2585: ---------------------------------- Summary: Jenkins web is not responsive Key: OVIRT-2585 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2585 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Edward Haas Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

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

23 Nov '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/652//artifact/exported-a… Cheers, Jenkins

1 0

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

22 Nov '18

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

1 0

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

22 Nov '18

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

1 0

[JIRA] (OVIRT-2584) Jenkins master UI very slow
by Eyal Edri (oVirt JIRA) 22 Nov '18

22 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2584?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2584: ----------------------------- Priority: Highest (was: High) > Jenkins master UI very slow > --------------------------- > > Key: OVIRT-2584 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2584 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master > Reporter: Emil Natan > Assignee: infra > Priority: Highest > > Jenkins master UI is very slow, sometimes reaching the timeout of the proxy before getting the page. > Looking at the machine I see the CPU utilization ~85-90%. It happened for 2 days in a row (21-22/11). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2584) Jenkins master UI very slow
by Emil Natan (oVirt JIRA) 22 Nov '18

22 Nov '18

Emil Natan created OVIRT-2584: --------------------------------- Summary: Jenkins master UI very slow Key: OVIRT-2584 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2584 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Master Reporter: Emil Natan Assignee: infra Priority: High Jenkins master UI is very slow, sometimes reaching the timeout of the proxy before getting the page. Looking at the machine I see the CPU utilization ~85-90%. It happened for 2 days in a row (21-22/11). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2583) ovirt-engine failing on master on test check_update_host
by Dafna Ron (oVirt JIRA) 22 Nov '18

22 Nov '18

Dafna Ron created OVIRT-2583: -------------------------------- Summary: ovirt-engine failing on master on test check_update_host Key: OVIRT-2583 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2583 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest ansible: Remove duplication of vnc_tls option - https://gerrit.ovirt.org/#/c/95169/ https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267 Mail sent to dev {noformat} [dron@dron post-002_bootstrap.py]$ egrep 89d99b74-fa6c-4d1d-a261-fb7ca7fcada2 lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log 2018-11-21 13:41:34,209-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 9ms 2018-11-21 13:41:34,224-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckCommand] (default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckCommand internal: false. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDSAction group EDIT_HOST_CONFIGURATION with role type ADMIN 2018-11-21 13:41:34,259-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 13ms 2018-11-21 13:41:34,273-05 INFO [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command: HostUpgradeCheckInternalCommand internal: true. Entities affected : ID: ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDS 2018-11-21 13:41:34,277-05 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 4ms 2018-11-21 13:41:34,281-05 DEBUG [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Inventory hosts: [lago-basic-suite-master-host-0] 2018-11-21 13:41:34,282-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Executing Ansible command: ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook, --ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check, --private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa, --inventory=/tmp/ansible-inventory2326258642232337463, /usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null] 2018-11-21 13:41:37,610-05 INFO [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Ansible playbook command has exited with value: 2 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to run check-update of host 'lago-basic-suite-master-host-0'. 2018-11-21 13:41:37,611-05 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to check if updates are available for host 'lago-basic-suite-master-host-0' with error message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.' 2018-11-21 13:41:37,616-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] EVENT_ID: HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates on host lago-basic-suite-master-host-0 with message 'Failed to run check-update of host 'lago-basic-suite-master-host-0'.'. [dron@dron post-002_bootstrap.py]$ {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[oVirt Jenkins] ovirt-node-ng-image_master_build-artifacts-fc28-x86_64 - Build # 122 - Failure!
by jenkins＠jenkins.phx.ovirt.org 22 Nov '18

22 Nov '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-fc2… Build Number: 122 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #122 [Yuval Turgeman] stdci: move build-artifacts to a v1 job [Barak Korren] Fix issue with `gitrepo` test fixture [Barak Korren] Enable direct pushes from pusher.py ----------------- Failed Tests: ----------------- No tests ran.

1 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Nov '18

22 Nov '18

Failed to run project_setup.sh for: #2586 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on ovirt-srv05.phx.ovirt.org-container-5.

1 0