- Infra - oVirt List Archives

[CQ]: 111910, 1 (ovirt-engine-api-metamodel) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Oct '20

27 Oct '20

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

1 0

[CQ]: 111886, 1 (ovirt-engine-api-metamodel) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Oct '20

27 Oct '20

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

1 0

oVirt infra daily report - unstable production jobs - 1356
by jenkins＠jenkins.phx.ovirt.org 26 Oct '20

26 Oct '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/1356//artifact/exported… Cheers, Jenkins

1 0

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

26 Oct '20

Failed to run project_setup.sh for: #24558 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 vm0141.workers-phx.ovirt.org.

1 0

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

26 Oct '20

Failed to run project_setup.sh for: #24559 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 vm0141.workers-phx.ovirt.org.

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Evgheni Dereveanchin (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-3049: --------------------------------------------- We do not perform github->gerrit sync at the moment, only the other way around. Adding support for this workflow would definitley require some work yet if we have more projects primarily hosted on GH and tracked via BZ this may be worth the effort. > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Anton Marchukov (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-3049: ---------------------------------------- [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] yes, exactly, it does and that hooks code is gerrit specific, so it will not work with github actions without rewriting. [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] so looks like we do not have a solution for github yet at least developed within our team. Maybe we can do it using github to gerrit sync and than use a hook it gerrit. That’s the only quick solution I can sync of. > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Barak Korren (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-3049: ------------------------------------- Its done by the Gerrit hooks no? Theoretically you could run similar code in a GitHub action to get similar results. > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Anton Marchukov (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-3049: ---------------------------------------- The implementation I am aware of if gerrit specific. Adding also [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] in case they developed some other hooks for kubevirt that could do it. > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Evgheni Dereveanchin (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-3049: --------------------------------------------- I know that on Gerrit this linking is done via hooks, [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] [~accountid:5aa0f39f5a4d022884128a0f] can we update BZ through GitHub? > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3049) ovirt-ansible-collection: Automatic bugzilla linking
by Evgheni Dereveanchin (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3049?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3049: ---------------------------------------- Issue Type: Task (was: By-EMAIL) > ovirt-ansible-collection: Automatic bugzilla linking > ---------------------------------------------------- > > Key: OVIRT-3049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3049 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > I now pushed my first PR to ovirt-ansible-collection [1]. > It has a Bug-Url link to [2]. > The bug wasn't updated with a link to the PR. Should it? Please make > it so that it does. > Also, perhaps, when creating new projects, do this automatically for > them (and ask what bugzilla product should be affected). > Thanks and best regards, > [1] https://github.com/oVirt/ovirt-ansible-collection/pull/151 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1844965 > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[JIRA] (OVIRT-3048) Jenkins environment broken
by Evgheni Dereveanchin (oVirt JIRA) 26 Oct '20

26 Oct '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3048?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-3048: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Jenkins environment broken > -------------------------- > > Key: OVIRT-3048 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3048 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Sandro Bonazzola > Assignee: infra > > Jenkins environment is broken: > ERROR: Command failed: > <https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_…> > # /usr/sbin/useradd -o -m -u 1012 -g 135 -d > /home/jenkins/workspace/ovirt-release_master_build-artifacts-el7-x86_64/ovirt-release > -n mockbuild > <https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_…> > <https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_…>mv: > missing destination file operand after > '/tmp/mock_logs.NrHWkusC/script' > <https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_…>Try > 'mv --help' for more information. > <https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_…>rmdir: > failed to remove './mock_logs.2uacsnGv': No such file or directory > from: https://jenkins.ovirt.org/job/ovirt-release_master_build-artifacts-el7-x86_… > -- > Sandro Bonazzola > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100149)

1 0

[oVirt Jenkins] cleanup-gated-ovirt-4.3 - Build #311 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Oct '20

26 Oct '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-4.3/311/ Build Name: #311 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 1621 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Oct '20

25 Oct '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-master/1… Build Number: 1621 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #1621 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1355
by jenkins＠jenkins.phx.ovirt.org 25 Oct '20

25 Oct '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/1355//artifact/exported… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 518 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Oct '20

25 Oct '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: 518 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #518 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1354
by jenkins＠jenkins.phx.ovirt.org 24 Oct '20

24 Oct '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/1354//artifact/exported… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-ovirt-master-centos-ovirt44-el8-x86_64 #576
by jenkins＠jenkins.phx.ovirt.org 24 Oct '20

24 Oct '20

See <https://jenkins.ovirt.org/job/system-sync_mirrors-ovirt-master-centos-ovirt…> Changes: ------------------------------------------ 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-sync_mirrors-ovirt-master-centos-ovirt…> The recommended git tool is: NONE 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 --version # 'git version 1.8.3.1' > 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:996) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1237) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1297) 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:1894) 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/': Failed to connect to 2600:1f18:26e2:3333::3333: Network is unreachable at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2450) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2051) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:84) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:573) 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:375) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73) 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:1800) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:1001) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.GeneratedMethodAccessor644.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.$Proxy105.execute(Unknown Source) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:994) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1237) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1297) 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:1894) 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 Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 512 - Failure!
by jenkins＠jenkins.phx.ovirt.org 23 Oct '20

23 Oct '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: 512 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #512 [Eitan Raviv] network: skip mac pool check used mac below 4.4 ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.004_basic_sanity.test_live_storage_migration Error Message: AssertionError: False != True after 600 seconds Stack Trace: engine_api = <ovirtsdk4.Connection object at 0x7fd7c00a1510> @order_by(_TEST_LIST) def test_live_storage_migration(engine_api): engine = engine_api.system_service() disk_service = test_utils.get_disk_service(engine, DISK0_NAME) correlation_id = 'live_storage_migration' disk_service.move( async=False, filter=False, storage_domain=types.StorageDomain( name=SD_ISCSI_NAME ), query={'correlation_id': correlation_id} ) assertions.assert_true_within_long(lambda: test_utils.all_jobs_finished(engine, correlation_id)) # Assert that the disk is on the correct storage domain, # its status is OK and the snapshot created for the migration # has been merged assertions.assert_true_within_long( lambda: engine_api.follow_link(disk_service.get().storage_domains[0]).name == SD_ISCSI_NAME ) vm0_snapshots_service = test_utils.get_vm_snapshots_service(engine, VM0_NAME) assertions.assert_true_within_long( > lambda: len(vm0_snapshots_service.list()) == 1 ) ../basic-suite-master/test-scenarios/004_basic_sanity.py:587: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../ost_utils/ost_utils/assertions.py:97: in assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) ../ost_utils/ost_utils/assertions.py:82: in assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=allowed_exceptions _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ func = <function <lambda> at 0x7fd7bbfdaaa0>, value = True, timeout = 600 allowed_exceptions = [], initial_wait = 0 error_message = 'False != True after 600 seconds' def assert_equals_within( func, value, timeout, allowed_exceptions=None, initial_wait=10, error_message=None ): allowed_exceptions = allowed_exceptions or [] with _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: if error_message is None: error_message = '%s != %s after %s seconds' % (res, value, timeout) > raise AssertionError(error_message) E AssertionError: False != True after 600 seconds ../ost_utils/ost_utils/assertions.py:60: AssertionError

1 3

oVirt infra daily report - unstable production jobs - 1353
by jenkins＠jenkins.phx.ovirt.org 23 Oct '20

23 Oct '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/1353//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 111862, 1 (ovirt-engine-api-explorer) failed "ovirt-4.3" system tests
by oVirt Jenkins 23 Oct '20

23 Oct '20

Change 111862,1 (ovirt-engine-api-explorer) 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/111862/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3995/

1 0

[CQ]: 111862, 1 (ovirt-engine-api-explorer) failed "ovirt-master" system tests
by oVirt Jenkins 23 Oct '20

23 Oct '20

Change 111862,1 (ovirt-engine-api-explorer) 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/111862/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/26567/

1 0

oVirt infra daily report - unstable production jobs - 1352
by jenkins＠jenkins.phx.ovirt.org 22 Oct '20

22 Oct '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/1352//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 111847, 2 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 22 Oct '20

22 Oct '20

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

1 0

[CQ]: 111847,2 (ovirt-system-tests) failed "ovirt-4.3" system tests
by oVirt Jenkins 22 Oct '20

22 Oct '20

Change 111847,2 (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/111847/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3993/

1 0