- Infra - oVirt List Archives

Build failed in Jenkins: system-mk_mirrors_index-yum #85291
by jenkins＠jenkins.phx.ovirt.org 20 May '20

20 May '20

See <https://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/85291/display/red…> Changes: ------------------------------------------ Started by upstream project "system-sync_mirrors-centos-sclo-rh-release-7.6-el7-x86_64" build number 630 originally caused by: Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <https://jenkins.ovirt.org/job/system-mk_mirrors_index-yum/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* # timeout=10 ERROR: Error fetching remote repo 'origin' hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:909) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1131) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at hudson.scm.SCM.checkout(SCM.java:505) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': Could not resolve host: gerrit.ovirt.org; Unknown error at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:569) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mirrors.phx.ovirt.org at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:998) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor933.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy90.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:907) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1131) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1167) at hudson.scm.SCM.checkout(SCM.java:505) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428) ERROR: Error fetching remote repo 'origin'

1 1

oVirt infra daily report - unstable production jobs - 1196
by jenkins＠jenkins.phx.ovirt.org 20 May '20

20 May '20

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

1 0

[JIRA] (OVIRT-2943) Very slow 'git pull' for gerrit.ovirt.org:ovirt-engine
by Artur Socha (oVirt JIRA) 19 May '20

19 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2943?page=com.atlassian.jira.… ] Artur Socha commented on OVIRT-2943: ------------------------------------ It seems the problem is gone. Since yesterday evening I have not noticed lags. > Very slow 'git pull' for gerrit.ovirt.org:ovirt-engine > --------------------------------------------------------- > > Key: OVIRT-2943 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2943 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Infra > Reporter: Artur Socha > Assignee: infra > > I have noticed that pulling updates for ovirt-engine takes very long now. In my case simple git pull took ~4minutes on master. > With GIT_TRACE=1 I observed low transfer speeds but even time to got to this point was unusually big. > Here is the git trace: https://pastebin.pl/view/ec457057 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

oVirt infra daily report - unstable production jobs - 1195
by jenkins＠jenkins.phx.ovirt.org 19 May '20

19 May '20

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

1 0

[Feedback needed] oVirt 4.4.0 Test week
by Sandro Bonazzola 18 May '20

18 May '20

Hi, oVirt team is planning to release oVirt 4.4.0 Ga in the next couple of weeks. oVirt 4.4.0 release candidate was released yesterday and we'd like to gather as much feedback as possible. Please join us testing this release candidate next week, starting Sunday May 10th 2020 till Friday May 15th 2020! We are going to coordinate the testing effort with a public Trello board at https://trello.com/b/5ZNJgPC3/ovirt-440-test-day You'll find instructions on how to use the board there. For joining the board you can use this link: https://trello.com/invite/b/5ZNJgPC3/f1b1826ee4902f348c44607765a15099/ovirt… If you have not an environment dedicated to testing, remember you can set up a few VMs and test the deployment with nested virtualization using your production environment creating a virtual test environment. In this case please be careful avoiding touching the production environment from the testing one. The oVirt team will monitor the Trello board, the #ovirt IRC channel on irc.oftc.net server and the users(a)ovirt.org mailing list to assist with the testing and debugging issues. Basic instructions for setting up a minimal system are available in release candidate announce at: https://lists.ovirt.org/archives/list/announce@ovirt.org/message/3QORBKVKTA… Release notes for this release candidate are available here: https://ovirt.org/release/4.4.0/ Thanks -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 1

[JIRA] (OVIRT-2943) Very slow 'git pull' for gerrit.ovirt.org:ovirt-engine
by Artur Socha (oVirt JIRA) 18 May '20

18 May '20

Artur Socha created OVIRT-2943: ---------------------------------- Summary: Very slow 'git pull' for gerrit.ovirt.org:ovirt-engine Key: OVIRT-2943 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2943 Project: oVirt - virtualization made easy Issue Type: Task Components: oVirt Infra Reporter: Artur Socha Assignee: infra I have noticed that pulling updates for ovirt-engine takes very long now. In my case simple git pull took ~4minutes on master. With GIT_TRACE=1 I observed low transfer speeds but even time to got to this point was unusually big. Here is the git trace: https://pastebin.pl/view/ec457057 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2942) [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80 oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt)
by Shlomi Zidmi (oVirt JIRA) 18 May '20

18 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2942?page=com.atlassian.jira.… ] Shlomi Zidmi reassigned OVIRT-2942: ----------------------------------- Assignee: Shlomi Zidmi (was: infra) > [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80 oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt) > ----------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2942 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2942 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Alertmanager_Bot > Assignee: Shlomi Zidmi > Labels: ALERT{alertname="MirrorIsOutOfSync"} > > Labels: > - alertname = MirrorIsOutOfSync > - instance = raw.githubusercontent.com:80 > - job = oVirt-mirrors-health > - url = http://ftp.snt.utwente.nl/pub/software/ovirt > Annotations: > - description = http://ftp.snt.utwente.nl/pub/software/ovirt (measured by oVirt-mirrors-health) has not been synced in the past two days. > Source: http://prometheus-0:9090/graph?g0.expr=mirror_health_check+%3E+172800&g0.ta… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2942) [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80 oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt)
by Alertmanager_Bot (oVirt JIRA) 18 May '20

18 May '20

Alertmanager_Bot created OVIRT-2942: --------------------------------------- Summary: [FIRING:1] MirrorIsOutOfSync (raw.githubusercontent.com:80 oVirt-mirrors-health http://ftp.snt.utwente.nl/pub/software/ovirt) Key: OVIRT-2942 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2942 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Alertmanager_Bot Assignee: infra Labels: - alertname = MirrorIsOutOfSync - instance = raw.githubusercontent.com:80 - job = oVirt-mirrors-health - url = http://ftp.snt.utwente.nl/pub/software/ovirt Annotations: - description = http://ftp.snt.utwente.nl/pub/software/ovirt (measured by oVirt-mirrors-health) has not been synced in the past two days. Source: http://prometheus-0:9090/graph?g0.expr=mirror_health_check+%3E+172800&g0.ta… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 109011, 2 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 18 May '20

18 May '20

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

1 0

[JIRA] (OVIRT-2940) Stuck job - running 8 days
by Evgheni Dereveanchin (oVirt JIRA) 18 May '20

18 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2940?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2940: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Stuck job - running 8 days > -------------------------- > > Key: OVIRT-2940 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2940 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > I found this stuck job in jenkins: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/ > Don't we have a timeout for killing run away jobs? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108164, 7 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 18 May '20

18 May '20

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

1 0

[JIRA] (OVIRT-2941) resources.ovirt.org doesn't reply on https
by Evgheni Dereveanchin (oVirt JIRA) 18 May '20

18 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2941?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2941: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > resources.ovirt.org doesn't reply on https > ------------------------------------------ > > Key: OVIRT-2941 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2941 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Sandro Bonazzola > Assignee: Evgheni Dereveanchin > > resources.ovirt.org doesn't reply on https; still reachable over ssh -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2941) resources.ovirt.org doesn't reply on https
by Sandro Bonazzola (oVirt JIRA) 18 May '20

18 May '20

Sandro Bonazzola created OVIRT-2941: --------------------------------------- Summary: resources.ovirt.org doesn't reply on https Key: OVIRT-2941 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2941 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Sandro Bonazzola Assignee: infra resources.ovirt.org doesn't reply on https; still reachable over ssh -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

oVirt infra daily report - unstable production jobs - 1194
by jenkins＠jenkins.phx.ovirt.org 18 May '20

18 May '20

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

1 0

otopi and change-queue
by Yedidyah Bar David 17 May '20

17 May '20

Hi all, I recently merged a patch to otopi: https://gerrit.ovirt.org/#/c/108590/ It failed in CQ: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23512/ Now commented there "ci re-merge", and it passed: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23736/ But didn't run basic-suite-master, and I do not understand if it will be published. Was anything changed in how change-queue works? Should I do anything else to make sure it's published? Thanks, -- Didi

2 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 11 - Failure!
by jenkins＠jenkins.phx.ovirt.org 17 May '20

17 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/11/ Build Number: 11 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #11 [jenkins CI] Auto create ovirt-4.3 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 005_network_by_label.assign_labeled_network Error Message: False != True after 180 seconds Stack Trace: Traceback (most recent call last): 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/005_network_by_label.py", line 149, in assign_labeled_network host_service, LABELED_NET_NAME)) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 180 seconds

1 1

oVirt infra daily report - unstable production jobs - 1193
by jenkins＠jenkins.phx.ovirt.org 17 May '20

17 May '20

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

1 0

oVirt infra daily report - unstable production jobs - 1192
by jenkins＠jenkins.phx.ovirt.org 16 May '20

16 May '20

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

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 1 - Failure!
by jenkins＠jenkins.phx.ovirt.org 15 May '20

15 May '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 1 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.002_bootstrap_pytest.test_verify_engine_backup Error Message: AssertionError: False != True after 600 seconds Stack Trace: prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7ff91385dcd0> @order_by(_TEST_LIST) def test_verify_engine_backup(prefix): engine_vm = prefix.virt_env.engine_vm() engine_vm.ssh( [ 'mkdir', '/var/log/ost-engine-backup', ], ) api = prefix.virt_env.engine_vm().get_api_v4() engine = api.system_service() with test_utils.TestEvent(engine, [9024, 9025]): #backup started event, completed result = engine_vm.ssh( [ 'engine-backup', '--mode=backup', '--file=/var/log/ost-engine-backup/backup.tgz', '--log=/var/log/ost-engine-backup/log.txt', ], ) > assert result.code == 0, \ 'Failed to run engine-backup with code {0}. Output: {1}'.format(result.code, result.out) ../basic-suite-master/test-scenarios/002_bootstrap_pytest.py:1303: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python2.7/contextlib.py:35: in __exit__ self.gen.throw(type, value, traceback) ../basic-suite-master/test_utils/__init__.py:290: in TestEvent lambda: /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:286: in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:273: in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function <lambda> at 0x7ff91367fc08>, value = True, timeout = 600 allowed_exceptions = [], initial_wait = 0 def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10 ): allowed_exceptions = allowed_exceptions or [] with utils.EggTimer(timeout) as timer: while not timer.elapsed(): try: res = func() if res == value: return except Exception as exc: if _instance_of_any(exc, allowed_exceptions): time.sleep(3) continue LOGGER.exception("Unhandled exception in %s", func) raise if initial_wait == 0: time.sleep(3) else: time.sleep(initial_wait) initial_wait = 0 try: raise AssertionError( > '%s != %s after %s seconds' % (res, value, timeout) ) E AssertionError: False != True after 600 seconds /usr/lib/python2.7/site-packages/ovirtlago/testlib.py:252: AssertionError

1 3

oVirt infra daily report - unstable production jobs - 1191
by jenkins＠jenkins.phx.ovirt.org 15 May '20

15 May '20

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

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 14 May '20

14 May '20

Failed to run project_setup.sh for: #21173 vdsm [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 vm0139.workers-phx.ovirt.org.

1 0

[CQ]: 109021, 2 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '20

14 May '20

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

1 0

[CQ]: 109020, 2 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '20

14 May '20

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

1 0

oVirt infra daily report - unstable production jobs - 1190
by jenkins＠jenkins.phx.ovirt.org 14 May '20

14 May '20

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

1 0

[CQ]: 109022, 1 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '20

14 May '20

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

1 0

[CQ]: 109019, 2 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 May '20

14 May '20

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

1 0

[CQ]: 109002, 1 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '20

13 May '20

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

1 0

[CQ]: 108909,9 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 13 May '20

13 May '20

Change 108909,9 (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/108909/9 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23683/

1 0

[JIRA] (OVIRT-2940) Stuck job - running 8 days
by Ehud Yonasi (oVirt JIRA) 13 May '20

13 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2940?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2940: ------------------------------------ Thanks for reporting Nir, You are right about the timeout - but that exists only during the actual code. In this case the slave was somehow out of storage / memory and it stuck during loading our stdci code. > Stuck job - running 8 days > -------------------------- > > Key: OVIRT-2940 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2940 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > I found this stuck job in jenkins: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/ > Don't we have a timeout for killing run away jobs? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2940) Stuck job - running 8 days
by Nir Soffer (oVirt JIRA) 13 May '20

13 May '20

Nir Soffer created OVIRT-2940: --------------------------------- Summary: Stuck job - running 8 days Key: OVIRT-2940 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2940 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I found this stuck job in jenkins: https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/5660/ Don't we have a timeout for killing run away jobs? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

2 1

[CQ]: 109003,1 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 13 May '20

13 May '20

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

1 0

[JIRA] (OVIRT-2939) Assign admin role for nsoffer for project ioprocess on github
by Anton Marchukov (oVirt JIRA) 13 May '20

13 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2939?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2939: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Assign admin role for nsoffer for project ioprocess on github > ------------------------------------------------------------- > > Key: OVIRT-2939 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2939 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > I need admin role for: > https://github.com/oVirt/ioprocess > So I can se tup webhooks and other stuff. > I have correct permissions in > https://github.com/oVirt/vdsm > https://github.com/oVirt/ovirt-imageio > Thanks, > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108995, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 13 May '20

13 May '20

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

1 0

[JIRA] (OVIRT-2924) Update mock_runner to support the new `--isolation` option for `mock`
by Barak Korren (oVirt JIRA) 13 May '20

13 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2924: -------------------------------- Summary: Update mock_runner to support the new `--isolation` option for `mock` (was: Fwd: Problem with the mock parameters) > Update mock_runner to support the new `--isolation` option for `mock` > --------------------------------------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2924) Fwd: Problem with the mock parameters
by Barak Korren (oVirt JIRA) 13 May '20

13 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2924: -------------------------------- Issue Type: Bug (was: By-EMAIL) > Fwd: Problem with the mock parameters > ------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2924) Fwd: Problem with the mock parameters
by Barak Korren (oVirt JIRA) 13 May '20

13 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2924: -------------------------------- Components: mock_runner > Fwd: Problem with the mock parameters > ------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: mock_runner > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

oVirt infra daily report - unstable production jobs - 1189
by jenkins＠jenkins.phx.ovirt.org 13 May '20

13 May '20

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

1 0

[CQ]: 108989,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 13 May '20

13 May '20

Change 108989,3 (ovirt-imageio) 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/108989/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23672/

1 0

[JIRA] (OVIRT-2924) Fwd: Problem with the mock parameters
by Lev Veyde (oVirt JIRA) 12 May '20

12 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Lev Veyde edited comment on OVIRT-2924 at 5/12/20 5:44 PM: ----------------------------------------------------------- According to the documentation --isolation=simple is equivalent to --old-chroot and --isolation=nspawn is equivalent to the --new-chroot option. I updated the patch to rely on the output of the mock -h, and use --isolation if it supports it. [https://gerrit.ovirt.org/#/c/108594/3/mock_configs/mock_runner.sh|https://g…] was (Author: lveyde(a)redhat.com) According to the documentation --isolation=simple is equivalent to --old-chroot and --isolation=nspawn is equivalent to the --new-root option. I updated the patch to rely on the output of the mock -h, and use --isolation if it supports it. [https://gerrit.ovirt.org/#/c/108594/3/mock_configs/mock_runner.sh|https://g…] > Fwd: Problem with the mock parameters > ------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2924) Fwd: Problem with the mock parameters
by Lev Veyde (oVirt JIRA) 12 May '20

12 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Lev Veyde commented on OVIRT-2924: ---------------------------------- According to the documentation --isolation=simple is equivalent to --old-chroot and --isolation=nspawn is equivalent to the --new-root option. I updated the patch to rely on the output of the mock -h, and use --isolation if it supports it. [https://gerrit.ovirt.org/#/c/108594/3/mock_configs/mock_runner.sh|https://g…] > Fwd: Problem with the mock parameters > ------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108949,6 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 12 May '20

12 May '20

Change 108949,6 (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/108949/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23667/

1 0

[CQ]: 108857, 20 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

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

1 0

[CQ]: 108880,7 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 12 May '20

12 May '20

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

1 0

[JIRA] (OVIRT-2939) Assign admin role for nsoffer for project ioprocess on github
by Nir Soffer (oVirt JIRA) 12 May '20

12 May '20

Nir Soffer created OVIRT-2939: --------------------------------- Summary: Assign admin role for nsoffer for project ioprocess on github Key: OVIRT-2939 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2939 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra I need admin role for: https://github.com/oVirt/ioprocess So I can se tup webhooks and other stuff. I have correct permissions in https://github.com/oVirt/vdsm https://github.com/oVirt/ovirt-imageio Thanks, Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108752, 2 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests
by oVirt Jenkins 12 May '20

12 May '20

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

1 0

[CQ]: 108952,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 May '20

12 May '20

Change 108952,2 (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/108952/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23658/

1 0

[CQ]: 108932,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 12 May '20

12 May '20

Change 108932,2 (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/108932/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23653/

1 0

[JIRA] (OVIRT-2924) Fwd: Problem with the mock parameters
by Lev Veyde (oVirt JIRA) 12 May '20

12 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2924?page=com.atlassian.jira.… ] Lev Veyde commented on OVIRT-2924: ---------------------------------- Just a note, it seems to happen randomly and happened again on ppc64le platform today: [https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/419/consol…] > Fwd: Problem with the mock parameters > ------------------------------------- > > Key: OVIRT-2924 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2924 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Forwarding to infra-support for analysis. > ---------- Forwarded message --------- > From: Lev Veyde <lveyde(a)redhat.com> > Date: Thu, Apr 23, 2020 at 2:02 PM > Subject: Problem with the mock parameters > To: infra <infra(a)ovirt.org> > Cc: Sandro Bonazzola <sbonazzo(a)redhat.com> > Hi, > it looks like we have some issues in the mock parameters on some of the > slaves > i.e.: > https://jenkins.ovirt.org/job/ovirt-release_standard-check-patch/387/consol… > note the ERROR: Option --old-chroot has been deprecated. Use > --isolation=simple instead. > Thanks in advance, > -- > Lev Veyde > Senior Software Engineer, RHCE | RHCVA | MCITP > Red Hat Israel > <https://www.redhat.com> > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YI577UNFDVGDB… > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 7dccacf (ovirt-ansible-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

A system test invoked by the "ovirt-master" change queue including change 7dccacf (ovirt-ansible-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 57e474d (ovirt-ansible-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 57e474d (ovirt-ansible-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://github.com/oVirt/ovirt-ansible-engine-setup/commit/7dccacf4a4d26e91… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/ovirt-ansible-engine-setup/commit/57e474de6e7c4c8e… For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23649/

1 0

[CQ]: 108752, 2 (ovirt-engine-nodejs-modules) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

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

1 0