January 2018 - Infra - oVirt List Archives

[CQ]: 82386, 1 (nsis-simple-service-plugin) failed "ovirt-4.1" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[JIRA] (OVIRT-1863) Service Alert: foreman/HTTP tcp connection going up and down
by Evgheni Dereveanchin (oVirt JIRA) 26 Jan '18

26 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1863?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1863: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Service Alert: foreman/HTTP tcp connection going up and down > ------------------------------------------------------------ > > Key: OVIRT-1863 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1863 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > > Hi, > we have been getting service disruption alerts for foreman http > The service is going up/down. > Can you please investigate this when you get a chance? > ***** Icinga ***** > Notification Type: PROBLEM > Service: HTTP tcp connection > Host: foreman > Address: 66.187.230.32 > State: CRITICAL > Date/Time: Fri Jan 26 08:42:38 UTC 2018 > ***** Icinga ***** > Notification Type: RECOVERY > Service: HTTP tcp connection > Host: foreman > Address: 66.187.230.32 > State: OK > Date/Time: Fri Jan 26 14:45:38 UTC 2018 > Additional Info: > HTTP OK: HTTP/1.1 200 OK - 4131 bytes in 1.563 second response time -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

1 0

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[ OST Failure Report ] [ oVirt Master (vcredist-x86) ] [ 26-01-2018 ] [ 002_bootstrap.verify_add_all_hosts ]
by Dafna Ron 26 Jan '18

26 Jan '18

Hi, We had a failure on test 002_bootstrap.verify_add_all_hosts in Ovirt Master I don't think the patch reported is related to the issue. >From what I can see, the host was locked when we tried to query its status and since we couldn't fence the host we exited in timeout. I do not think the reported patch was the reason for failure. *Link and headline of reported patches: https://gerrit.ovirt.org/#/c/82234/1 <https://gerrit.ovirt.org/#/c/82234/1> - Initial import from ovirt-wgt-toolchainLink to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5123/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5123/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5123/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5123/artifact/>(Relevant) error snippet from the log: <error>2018-01-26 06:37:31,022-05 INFO [org.ovirt.engine.core.bll.RefreshHostCapabilitiesCommand] (ForkJoinPool-1-worker-4) [75b3e642] Failed to Acquire Lock to object 'EngineLock:{exclusiveLocks='[52ee1a61-31c3-4af8-ae28-65f0953f1804=VDS, HOST_NETWORK52ee1a61-31c3-4af8-ae28-65f0953f1804=HOST_NETWORK]', sharedLocks=''}'2018-01-26 06:37:31,022-05 WARN [org.ovirt.engine.core.bll.RefreshHostCapabilitiesCommand] (ForkJoinPool-1-worker-4) [75b3e642] Validation of action 'RefreshHostCapabilities' failed for user SYSTEM. Reasons: VAR__ACTION__REFRESH,VAR__TYPE__HOST_CAPABILITIES,ACTION_TYPE_FAILED_OBJECT_LOCKED2018-01-26 06:37:31,373-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (SSL Stomp Reactor) [1d883766] MESSAGEcontent-length:80destination:jms.topic.vdsm_responsescontent-type:application/jsonsubscription:ce434ca4-0c91-44b6-843a-7f8cff40d8e4{"jsonrpc": "2.0", "id": "8f1c8652-044c-4051-85d7-3d290ee2014f", "result": true}^@2018-01-26 06:37:31,374-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) [] Message received: {"jsonrpc": "2.0", "id": "8f1c8652-044c-4051-85d7-3d290ee2014f", "result": true}2018-01-26 06:37:31,374-05 ERROR [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) [] Not able to update response for "8f1c8652-044c-4051-85d7-3d290ee2014f"2018-01-26 06:37:31,376-05 DEBUG [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (SSL Stomp Reactor) [1d883766] MESSAGEcontent-length:802018-01-26 06:37:35,147-05 ERROR [org.ovirt.engine.core.bll.pm.FenceProxyLocator] (EE-ManagedThreadFactory-engineScheduled-Thread-8) [78ab5d20] Can not run fence action on host 'lago-basic-suite-master-host-0', no suitable proxy host was found.</error>*

1 0

[JIRA] (OVIRT-1863) Service Alert: foreman/HTTP tcp connection going up and down
by Dafna Ron (oVirt JIRA) 26 Jan '18

26 Jan '18

Dafna Ron created OVIRT-1863: -------------------------------- Summary: Service Alert: foreman/HTTP tcp connection going up and down Key: OVIRT-1863 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1863 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Dafna Ron Assignee: infra Hi, we have been getting service disruption alerts for foreman http The service is going up/down. Can you please investigate this when you get a chance? ***** Icinga ***** Notification Type: PROBLEM Service: HTTP tcp connection Host: foreman Address: 66.187.230.32 State: CRITICAL Date/Time: Fri Jan 26 08:42:38 UTC 2018 ***** Icinga ***** Notification Type: RECOVERY Service: HTTP tcp connection Host: foreman Address: 66.187.230.32 State: OK Date/Time: Fri Jan 26 14:45:38 UTC 2018 Additional Info: HTTP OK: HTTP/1.1 200 OK - 4131 bytes in 1.563 second response time -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

1 0

[CQ]: 82386, 1 (nsis-simple-service-plugin) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

Change 82386,1 (nsis-simple-service-plugin) 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/82386/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/361/

1 0

[CQ]: 80073, 2 (ovirt-js-dependencies) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 82632,1 (py2exe-py2.7) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 82638,1 (python-windows) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-master" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 82667,1 (pywin32-py2.7) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 86819, 2 (cockpit-ovirt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

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

26 Jan '18

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

1 0

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

26 Jan '18

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

1 0

[CQ]: 86811, 1 (imgbased) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 86810, 1 (imgbased) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Jan '18

26 Jan '18

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

1 0

[CQ]: 86734,1 (ovirt-engine) failed "ovirt-4.1" system tests
by oVirt Jenkins 25 Jan '18

25 Jan '18

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

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 23 - Failure!
by jenkins＠jenkins.phx.ovirt.org 25 Jan '18

25 Jan '18

------=_Part_263_1084542245.1516709967862 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el7-… Build Number: 23 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #23 [Gal Ben Haim] ost: Add 4.2 to the manual job [Gal Ben Haim] ost: Adding 'he-basic-ansible' to the manual job [Daniel Belenky] Add line brak before mock_enable_network [Gal Ben Haim] ost: Fix Lago custom repo [Greg Sheremeta] ovirt-js-dependencies: add jobs for fc27, add 4.2 branch [Nir Soffer] ioprocess: Remove Fedora 26 builds [Yuval Turgeman] image-ng: move chroot distro to el7 [Sandro Bonazzola] ovirt-engine: add 3.6-els branch [Sandro Bonazzola] build: switch to ovirt-release42 ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_263_1084542245.1516709967862--

1 1

[JIRA] (OVIRT-1862) vm0002.workers-phx.ovirt.org malfunction
by Daniel Belenky (oVirt JIRA) 25 Jan '18

25 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1862?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1862: ------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > vm0002.workers-phx.ovirt.org malfunction > ---------------------------------------- > > Key: OVIRT-1862 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1862 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > Hey, > It seems that something bad is happening on vm0002.workers-phx.ovirt.org. Jobs fail with AccessDeniedException on this slave. > Can you please check what happened? > We've put the slave offline for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

1 0

[JIRA] (OVIRT-1862) vm0002.workers-phx.ovirt.org malfunction
by Daniel Belenky (oVirt JIRA) 25 Jan '18

25 Jan '18

Daniel Belenky created OVIRT-1862: ------------------------------------- Summary: vm0002.workers-phx.ovirt.org malfunction Key: OVIRT-1862 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1862 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra Hey, It seems that something bad is happening on vm0002.workers-phx.ovirt.org. Jobs fail with AccessDeniedException on this slave. Can you please check what happened? We've put the slave offline for now. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

1 0

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available
by sbonazzo (oVirt JIRA) 25 Jan '18

25 Jan '18

sbonazzo created OVIRT-1861: ------------------------------- Summary: Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available Key: OVIRT-1861 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1861 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra 2018-01-24 13:47 GMT+01:00 Arman Khalatyan <arm2arm(a)gmail.com>: > Thanks for the announcement. > A little comment: could you please fix the line yum install > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm > <http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm%3E> > There is an extra '<' symbol there since 4.0.x :=) > > Thanks for the feedback, I opened https://github.com/oVirt/ovirt-site/issues/1503 to track this. Opening a ticket on infra as well for further investigations. > > On Wed, Jan 24, 2018 at 12:00 PM, Lev Veyde <lveyde(a)redhat.com> wrote: > >> The oVirt Project is pleased to announce the availability of the oVirt >> 4.1.9 release, as of January 24th, 2017 >> >> This update is the ninth in a series of stabilization updates to the 4.1 >> series. >> >> Please note that no further updates will be issued for the 4.1 series. >> We encourage users to upgrade to 4.2 series to receive new features and >> updates. >> >> This release is available now for: >> * Red Hat Enterprise Linux 7.4 or later >> * CentOS Linux (or similar) 7.4 or later >> >> This release supports Hypervisor Hosts running: >> * Red Hat Enterprise Linux 7.4 or later >> * CentOS Linux (or similar) 7.4 or later >> * oVirt Node 4.1 >> >> See the release notes [1] for installation / upgrade instructions and >> a list of new features and bugs fixed. >> >> Notes: >> - oVirt Appliance is already available >> - oVirt Live is already available [2] >> - oVirt Node will be available soon [2] >> >> Additional Resources: >> * Read more about the oVirt 4.1.9 release highlights:http://www.ovirt.or >> g/release/4.1.9/ >> * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt >> * Check out the latest project news on the oVirt blog: >> http://www.ovirt.org/blog/ >> >> [1] http://www.ovirt.org/release/4.1.9/ >> [2] http://resources.ovirt.org/pub/ovirt-4.1/iso/ >> >> -- >> >> Lev Veyde >> >> Software Engineer, RHCE | RHCVA | MCITP >> >> Red Hat Israel >> >> <https://www.redhat.com> >> >> lev(a)redhat.com | lveyde(a)redhat.com >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)

1 0

[CQ]: 86757, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Jan '18

25 Jan '18

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

2 1

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

25 Jan '18

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

1 0

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

25 Jan '18

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

1 0