Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master] [ 09/08/2017 ] [ 001_upgrade_engine.test_initialize_engine ]

gt; > https://buildlogs.centos.org/centos/7/opstools/x86_64/logging/rubygem-fluent-plugin-secure-forward-0.4.5-1.el7.noarch.rpm > > <https://buildlogs.centos.org/centos/7/opstools/x86_64/logging/rubygem-fluent-plugin-secure-forward-0.4.5-1.el7.noarch.rpm> > > The erro

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master] [ 09/08/2017 ] [ 001_upgrade_engine.test_initialize_engine ]

s/7/opstools/x86_64/logging/rubygem-fluent-plugin-secure-forward-0.4.5-1.el7.noarch.rpm> > > The error is not about this package, > > > > > > > > > > > On Wed, Aug 9, 2017 at 5:56 PM, Dafna Ron <d...@redhat.com > &

Re: [ovirt-devel] [ ovirt-devel ] [ OST Failure Report ] [ oVirt Master ] [ 002_bootstrap ] [ 17/08/17 ]

Daniel, the link below is for failed test 002_bootstrap.add_secondary_storage_domains - is that the correct link? If so, the error is in node01 and from what I can see, there is a race between creating the target for the secondary domain and the mount command sent from the host. The reason I

[ovirt-devel] Subject: [ OST Failure Report ] [ oVirt $VER ] [ $DATE ] [ TEST NAME ]

** *Hi, * * ** vm failed to run with libvrt unsupported configuration (see error below) since the patch is related to 4.2 xml configuration and the vm failed to run on unsupported configuration I suspect its related - can you please have a closer look? ** ** here is a grep from logs on vm

Re: [ovirt-devel] Subject: [ OST Failure Report ] [ oVirt $VER ] [ $DATE ] [ TEST NAME ]

Thank you :) I will keep an eye on the tests On 07/07/2017 09:43 AM, Arik Hadas wrote: > > > בתאריך 6 ביולי 2017 11:13 PM,‏ "Arik Hadas" <aha...@redhat.com > <mailto:aha...@redhat.com>> כתב: > > > > On Thu, Jul 6, 2017 at 8:40 PM, Dafna Ron

Re: [ovirt-devel] Subject: [ OST Failure Report ] [ oVirt master ] [ 07-07-2017 ] [ 004_basic_sanity.vm_run ]

e vm id from logs: http://pastebin.test.redhat.com/501085 here is a link to full logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7501/artifact/ Can you please have a look? Thanks, Dafna On 07/07/2017 10:03 AM, Dafna Ron wrote: > Thank you :) > I will keep an e

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 03-07-2017 ] [ 006_migrations.migrate_vm ]

This issue is reproduced locally as well. you can run the following to reproduce locally ./run_suite.sh -s http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-x86_64/2694/ basic-suite-master you will have the environment still running which would allow to view the live environment. if

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ Aug. 8th 2017 ] [ 001_upgrade_engine.test_initialize_engine ]

** *Hi, * * ** We see a sporadic failure in the upgrade test. from what I can see from the log it is related to the firewalD package. Test failed: *001_upgrade_engine.test_initialize_engine* Link to suspected patches: Link to Job:

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 09/08/2017 ] [ ovirt-hosted-engine-ha ]

Hi, We have a failure in ovirt-hosted-engine-ha which shows that project ovirt-hosted-engine-ha_master_build-artifacts-el7-x86_64 has failed to build. in ovirt-hosted-engine-ha_master_build-artifacts-el7-x86_64 we have failure due to package dependency. ** ** *Test failed:

[ovirt-devel] [ OST Failure Report ] [ oVirt Master] [ 09/08/2017 ] [ 001_upgrade_engine.test_initialize_engine ]

Hi, We failed upgrade_engine.test_initialize_engine. the failure is caused by a package that I removed from the ovirt-snapshot-master for JIRA: OVIRT-1097 I restored the package and the tests should succeed. ** *Test

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-05-2017 ] [ 004_basic_sanity.hotunplug_disk ]

** *Hi All, * * ** *We are seeing the same failure**sporadically**in *three*different places (hotunplug disk). * *We think this is a race condition which was introduced to OST with the the live storage migration test (lock on the disk is preventing the hotunplug). * Test failed: [

Re: [ovirt-devel] [ovirt-system-tests] Failed after fluentd rpm ubdate

We have var logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7191/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-003_00_metrics_bootstrap.py/lago-basic-suite-master-engine/ I egreped fluentd from engine's host messages files:

[ovirt-devel] Fwd: Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #501

Hi, We have a failure on centos sync. Anyone can take a look? Thanks, Dafna Forwarded Message Subject:Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #501 Date: Wed, 14 Jun 2017 16:39:03 + (UTC) From: jenk...@jenkins.phx.ovirt.org

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt HE master ] [ 17/09/17 ] [ engine-setup ]

On 09/18/2017 11:12 AM, Simone Tiraboschi wrote: > > > On Mon, Sep 18, 2017 at 12:09 PM, Simone Tiraboschi > > wrote: > > > > On Sun, Sep 17, 2017 at 11:14 AM, Eyal Edri > wrote: > > > >

[ovirt-devel] Subject: [ OST Failure Report ] [ master ] [ 19-09-2017E ] [ 004_basic_sanity ]

Hi, Lago reports add_console was the failed action: ... In the engine log I can see that both hosts fail to respond and that we have also have errors in ansible for invalid services in fedora. CQ reports a network patch as the probable cause. See further info below ** *Link to suspected

[ovirt-devel] Subject: [ OST Failure Report ] [ master ] [ 20-09-2017] [ No Test Failed - missing packages in fc25 ]

Hi, CQ reported a failure in one of the builds and looking at the console I found that we had a failure before the OST started due to: ovirt-hosted-engine-ha_master_build-artifacts-fc25-x86_64 (67) failed building The build failed of ovirt-hosted-engine-ha_master_build-artifacts-fc25-x86_64

Re: [ovirt-devel] Subject: [ OST Failure Report ] [ master ] [20-09-2017 ] [ post-002_bootstrap.py ]

n Wed, Sep 20, 2017 at 2:11 PM, Martin Perina <mper...@redhat.com> wrote: >> Ondro, could you please take a look? >> >> On Wed, Sep 20, 2017 at 1:07 PM, Dafna Ron <d...@redhat.com> wrote: >>> Hi, >>> >>> We have a failure in test post-002

[ovirt-devel] Subject: [ OST Failure Report ] [ master ] [20-09-2017 ] [ post-002_bootstrap.py ]

Hi, We have a failure in test post-002_bootstrap.py from the logs I can see that lago has an unhandled exception from ovirt sdk which makes sense since the patch reported on CQ is a change to the sdk. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/82022/* * Link to Job:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 13-10-2017 ] [ 002_bootstrap.add_dc ]

Juan is verifying the fix now: https://gerrit.ovirt.org/82768 On 10/13/2017 02:15 PM, Dafna Ron wrote: > > Hi, > > We have a failure on test 002_bootstrap.add_dc. > > Juan said he would send a patch in a few minutes. > > > ** > > *Link to suspected patches: h

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 13-10-2017 ] [ 002_bootstrap.add_dc ]

Hi, We have a failure on test 002_bootstrap.add_dc. Juan said he would send a patch in a few minutes. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/82401/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3122/ Link to all logs:

[ovirt-devel] CQ failure due to ovirt-guest-agent_master_build-artifacts-el7-x86_64/

Hi, CQ is reporting failure due to failed build of ovirt-guest-agent_master_build-artifacts-el7-x86_64 first failure for guest agent was reported here: http://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-el7-x86_64/42/ Latest failure is here:

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 06-10-2017 ] [ 002_bootstrap.py ]

Hi, We have a failure in CQ on 002_bootstrap. It seems from the setup logs that both hosts failed to be deployed. I also see in the lago logs that the issue with the sdk. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/82525/* * Link to Job:

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 12-10-2017 ] [003_00_metrics_bootstrap.configure_metrics ]

Hi, We had a failure to configure metrics in ovirt-system-tests which caused metrics_bootstrap to fail. The patch that was reported as the cause is below. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/82686/* * Link to Job:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 12-10-2017 ] [003_00_metrics_bootstrap.configure_metrics ]

xported-artifacts/basic-suit-master-el7/003_00_metrics_bootstrap.py.junit.xml >> >> On Thu, Oct 12, 2017 at 12:26 PM, Dafna Ron <d...@redhat.com> wrote: >> > I agree, seems to be unrelated to my patch. > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 12-10-2017 ] [003_00_metrics_bootstrap.configure_metrics ]

Adding Eyal, Barak and Sandro and removing Victor. Personally, I do not mind taking on this task, but I think that I would need help in creating such a task. On 10/12/2017 06:51 PM, Yaniv Kaul wrote: > > > On Thu, Oct 12, 2017 at 2:36 PM, Dafna Ron <d...@redhat.com > <mail

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-09-2017 ] [ 003_00_metrics_bootstrap.configure_metrics ]

Hi, We had failure in OST last night which seems to be related to two fluentd configuration patchs. I found that the error is actually in the deployment and can be found in the lago log. I am not sure it's related but I am also seeing unexpected errors in the vdsm log for getDeviceList:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-09-2017 ] [ 004_basic_sanity.disk_operations ]

Please note that 004_basic_sanity.disk_operations is still failing: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/2941/ thanks, Dafna On 09/28/2017 12:05 PM, Dafna Ron wrote: > > Hi, > > We had a failure in OST for basic disk operation. > > from what I

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-09-2017 ] [ 003_00_metrics_bootstrap.configure_metrics ]

On 09/29/2017 11:35 AM, Yaniv Kaul wrote: > > > On Fri, Sep 29, 2017 at 1:19 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > Hi, > > We had failure in OST last night which seems to be related to two > fluentd configuration

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-09-2017 ] [ 004_basic_sanity.disk_operations ]

Hi, We had a failure in OST for basic disk operation. from what I can see in the log, there is an issue deleting a snapshot image and the issue is related to the live storage migration. However, a second pair of eyes would help since I can see engine reporting the error on failed delete while

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 28-09-2017 ] [ 004_basic_sanity.disk_operations ]

-master_change-queue-tester/2913/ On 09/28/2017 12:05 PM, Dafna Ron wrote: > > Hi, > > We had a failure in OST for basic disk operation. > > from what I can see in the log, there is an issue deleting a snapshot > image and the issue is related to the live storage migration. >

[ovirt-devel] failure in CQ due to failed build artifacts

hi, we have some failures in CQ and they seem to be related to failure to build engine packages. 1. first failure reported: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64/5313/ This happened due to failed build:

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 09-10-2017] [ 001_initialize_engine.initialize_engine, 001_upgrade_engine.test_initialize_engine, 001_upgrade_engine.test_initialize_engine ]

Hi, We had a failure in initializing engine. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/82283/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3053/ ** http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3054/ Link to all logs: **

Re: [ovirt-devel] engine-setup error: "can only concatenate list (not "tuple") to list"

yes. it has been reported earlier today. engine initialization failed on master, and upgrade suites. On 10/09/2017 12:42 PM, Jakub Niedermertl wrote: > Hi all, > > anyone else is experiencing engine-setup error like this in dev > installation? > > > --== DATABASE CONFIGURATION

[ovirt-devel] Failure in CQ testing

Hi, We have a CQ failure with the error: error: [Errno 98] Address already in use * Link to suspected patches: This failure is pointing to: https://gerrit.ovirt.org/#/c/81704/ Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3055/ Link to all logs:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

/artifact/exported-artifacts/upgrade-from-release-suit-master-el7/test_logs/upgrade-from-release-suite-master/post-001_initialize_engine.py/lago-upgrade-from-release-suite-master-engine/_var_log/messages/*view*/ > > > On Fri, Nov 24, 2017 at 8:16 PM, Dafna Ron >

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 27-11-2017] [ 001_initialize_engine.test_initialize_engine ]

** *Hi*, ** * ** We have a failure reported in ovirt 4.1**on ovirt-imageio not starting and causing initialize_engine to fail I am not sure the reported patch is related**but it was reported by cq as the cause of the failure. Link and headline of suspected patches: Renamed

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 22-11-2017 ] [ 002_bootstrap.add_dc ]

Hi, I am not sure we should be alerting on 4.2 versions yet but since we are getting several cq failures for the same reasons and test, I decided this should be communicated. The failed test is 002_bootstrap.add_dc in OST 4.2. and all are pointing to one patch. Remove mandatory option for

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

wrote: > > > On Wed, Nov 22, 2017 at 7:55 PM, Nir Soffer <nsof...@redhat.com > <mailto:nsof...@redhat.com>> wrote: > > > > On Wed, Nov 22, 2017 at 7:15 PM Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> w

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

Hi, We have a failing on test 001_initialize_engine.test_initialize_engine. This is failing with error Failed to start service 'ovirt-imageio-proxy ** *Link and headline ofto suspected patches: * *** build: Make resulting RPMs architecture-specific - https://gerrit.ovirt.org/#/c/84534/

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

There was an issue with the mirrors and I see the patch merged 7 hours ago so its possible it was a late alert. On 11/23/2017 03:58 PM, Viktor Mihajlovski wrote: > On 23.11.2017 16:29, Dafna Ron wrote: >> Hi, >> >> We have a failing on test 001_initialize_engine.t

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

) >> [bll.jar:] >> at org.ovirt.engine.core.bll.Backend.endAction(Backend.java:536) >> [bll.jar:] > > On Thu, Nov 23, 2017 at 4:44 PM, Allon Mureinik <amure...@redhat.com > <mailto:amure...@redhat.com>> wrote: > > > -- Forwarded message ---

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 20-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

gin now? > > On Wed, Nov 29, 2017 at 12:07 PM Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > * > > Hi, > > ** > > We have failed cq with ovirt-imageio failing to start on upgrade > suite*. *I can still only see

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 20-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

* Hi, ** We have failed cq with ovirt-imageio failing to start on upgrade suite*. *I can still only see errors**in the messages log. ** I'm writing the reported patch but I don't think it has anything to do with this issue. Link and headline of suspected patches: restapi: Enable update to

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 20-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

David wrote: > On Wed, Nov 29, 2017 at 1:00 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > this is the plugin info from steup log but I don't see anything > more than we have seen except a timeout. > > https://past

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

(InterceptorContext.java:509) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73) [weld-core-impl-2.4.3.Final.jar:2.4.3.Final] ] : On 11/23/2017 06:04 PM, Dafna Ron wrote: > Thanks, > I am not sure the exception i

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

On 11/22/2017 05:55 PM, Nir Soffer wrote: > > > On Wed, Nov 22, 2017 at 7:15 PM Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > Hi, > > we have a failure in 004_basic_sanity.verify_add_vm_template. > > The error seems

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

issue was resolved by Ala's patch. Thanks :) Dafna On 11/23/2017 06:52 PM, Dafna Ron wrote: > I am still seeing an exception in latest failure: > > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4064/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-sui

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

t; On Thu, Nov 23, 2017 at 5:29 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > Hi, > > We have a failing on test > 001_initialize_engine.test_initialize_engine. > > This is failing with error Failed to start service >

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 22-11-2017 ] [ 004_basic_sanity.verify_add_vm_template ]

Hi, we have a failure in 004_basic_sanity.verify_add_vm_template. The error seems to be a failure from the api request since although I am seeing errors in the logs I am not sure they are the cause. ** *Link and headline ofto suspected patches: * * core: Cleanup BaseImagesCommand code -

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 20-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

On 11/30/2017 03:03 PM, Yedidyah Bar David wrote: > On Wed, Nov 29, 2017 at 4:57 PM, Yedidyah Bar David <d...@redhat.com> wrote: >> On Wed, Nov 29, 2017 at 3:56 PM, Dafna Ron <d...@redhat.com> wrote: >>> we had a failure on 002_bootstrap.verify_add_hosts but the err

[ovirt-devel] [ OST Failure Report ] [ oVirt Hosted-Engine ] [ 17-12-2017 ] [ post-002_bootstrap.py ]

Hi, We are failing OST for HE deployment. The failures started on 12/12 and latest failure is today, 17/12. ** *Link and headline of suspected patches: * *** OST: avoid excluding ovirt-engine-appliance from base repo- https://gerrit.ovirt.org/#/c/85439/ Link to Job:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 12-12-2017 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]

gt; ret = func(*args, **kwargs) >> File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 394, in >> hotunplugNic >> return self.vm.hotunplugNic(params) >> File "", line 2, in hotunplugNic >> File "/usr/lib/python2.7

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 12-12-2017 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]

Hi, We have a failure on test 098_ovirt_provider_ovn.use_ovn_provider but I am not sure how the reported patch is related to the failure. ** *Link and headline of suspected patches: * *https://gerrit.ovirt.org/#/c/85147/ - virt: Fix flipped condition in hotunplugNic* ** *Link to Job:*

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 14-12-2017 ] [ 004_basic_sanity.disk_operations ]

Hi, We have a failure on basic suite on test: 004_basic_sanity.disk_operations I think that we query a snapshot that was already deleted successfully and report the snapshot as gone. and that is because of a different error in update vm query which happens before. * Link and headline of

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 14-11-2017 ] [ 002_bootstrap.add_hosts ]

Hi, We had a failure in upgrade suite for 002_bootstrap.add_hosts. I am not seeing any error that can suggest on an issue in engine. I can see in the host messages host that we have stopped writing to the log for 15 minutes and it may suggest that there is something that is keeping the host from

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 20-11-1017 ] [ 002_bootstrap.verify_add_all_hosts ]

Hi, We had a failure in OST for test 002_bootstrap.verify_add_all_hosts. >From the logs I can see that vdsm on host0 was reporting that it cannot find the physical volume but eventually the storage was created and is reported as responsive. However, Host1 is reported to became non-operational

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 20-11-2017 ] [004_basic_sanity.vm_run ]

Hi, We have a failure in OST on test 004_basic_sanity.vm_run. it seems to be an error in vm type which is related to the patch reported. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/84343/* * Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3922

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 20-11-1017 ] [ 002_bootstrap.verify_add_all_hosts ]

On 11/20/2017 01:16 PM, Yaniv Kaul wrote: > > > On Mon, Nov 20, 2017 at 3:10 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > Hi, > > We had a failure in OST for test 002_bootstrap.verify_add_all_hosts. > > From the logs

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 16-11-2017 ] [ 002_bootstrap.add_dc ]

Hi, we have a CQ failure in add_dc test. I can see at engine long that we have an issue with 'extension.aaa.jdbc.binding.api.AuthnExtension' I don't think that the patch reported was the actual cause of the failure. Yesterday we were failing on missing package ovirt-cockpit-sso which we added to

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 14-11-2017 ] [ 002_bootstrap.add_hosts ]

Tue, Nov 14, 2017 at 5:48 PM, Dafna Ron <d...@redhat.com> wrote: >> Hi, >> >> We had a failure in upgrade suite for 002_bootstrap.add_hosts. I am not >> seeing any error that can suggest on an issue in engine. >> >> I can see in the host messages host that

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 15-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

Hi, We have a few alerts from cq all pointing to the same patch. Adding Sandro since he's working on fixing the packages issue and resolve this. ** *Link to suspected patches: **https://gerrit.ovirt.org/#/c/83852/* ** ** *Link to Job:* *** *

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 06-11-2017] [ 002_bootstrap.add_hosts ]

Hi, We have a failure in test 002_bootstrap.add_hosts I can see that the hosts are added but there are errors in engine.log that suggest there is a problem with crypto. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83367/* * Link to Job:

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 06-11-2017 ] [ 002_bootstrap.verify_add_hosts ]

adding Didi. On 11/06/2017 11:51 AM, Ala Hino wrote: > Suspected patch (https://gerrit.ovirt.org/#/c/83612/) is about cold > merge and has nothing to do with host deploy. > > On Mon, Nov 6, 2017 at 1:39 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wr

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 06-11-2017 ] [ 002_bootstrap.verify_add_hosts ]

Hi, We failed test 002_bootstrap.verify_add_hosts I can see we only tried to install one of the hosts (host-0) and failed. the second host has no log which means we did not try to deploy it. The error suggests that we ovirt-imageio-daemon failed to start. However, there is another message that

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 01 Nov 2017 ] [ 098_ovirt_provider_ovn.test_ovn_provider_rest ]

Hi, 098_ovirt_provider_ovn.test_ovn_provider_rest failed on removing the interface from a running vm. I have seen this before, do we perhaps have a race in OST where the vm is still running at times? ** *Link to suspected patches: Patch reported is below but I am suspecting its a race and not

[ovirt-devel] Network is already in use by interface virbr2 error

Hi, We have an ongoing issue with some builds failing due to failure to clean network from libvirt. the error is: libvirtError: internal error: Network is already in use by interface virbr2 we are working to fix the issue and will update once it's resolved. Thanks, Dafna

Re: [ovirt-devel] Network is already in use by interface virbr2 error

the lago > virtual host? > What calls libvirt and sees this error? Who tries to create the > virbr2 network? > > It smells like a lago/ost problem, not an ovirt one. > > > On Thu, Nov 2, 2017 at 5:39 PM, Dafna Ron <d...@redhat.com > <mailto:d...@

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 06-11-2017 ] [ 002_bootstrap.verify_add_hosts ]

.@redhat.com>> wrote: > > On Mon, Nov 6, 2017 at 1:57 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > adding Didi. > > > > > > On 11/06/2017 11:51 AM, Ala Hino wrote: > > > > Susp

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

Hi, We had a failure in installing engine with a dependency error between ovirt-engine-backend and vdsm-jsonrpc-java Please note that we have other issues which are not related to this patch so it might be hard to find this issue. I also added the lago log where you can find the package

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 09-11-2017 ] [ 001_upgrade_engine.test_initialize_engine ]

On 11/09/2017 02:03 PM, Martin Perina wrote: > > > On Thu, Nov 9, 2017 at 2:49 PM, Dafna Ron <d...@redhat.com > <mailto:d...@redhat.com>> wrote: > > Hi, > > We had a failure in installing engine with a dependency error > between ovirt-engine-backe

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 07-11-2017 ] [ 004_basic_sanity.disk_operations ]

so we will soon see if it is > indeed broken or if it was just a glitch. > > Bests, > > > On 11/07/2017 05:32 PM, Dafna Ron wrote: >> >> Hi, >> >> We have a failure in test 004_basic_sanity.disk_operations. >> >> From the log I can see that

[ovirt-devel] Infra related events message - review needed

Hi, We had some confusion last week when I sent a message about an infrastructure related issue we have found and people thought I was reporting an error on OST so I decided that perhaps it would be a good idea to create a general message that would alert people on an on-going infra event and not

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ Nov 1st 2017 ] [ 002_bootstrap.add_master_storage_domain]

Hi, There are three reported failures on the same test: 002_bootstrap.add_master_storage_domain This seems to be related to packages issues. Please note that all 3 suits failed. Basic suit failed because of ovirt-host-4.2.0-0.0 and i think all related issues came from there. upgrade suits

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ Nov 1st 2017 ] [002_bootstrap.add_dc, 002_bootstrap.add_master_storage_domain ]

Hi, we have failures in 4.1 imagebased. I think it's also related to the same package from 4.2 that is downloaded in the 4.1 repo. 2017-11-01 13:17:53,817::ssh.py::ssh::96::lago.ssh::DEBUG::Command 10946280 on lago-basic-suite-4-1-host-0 errors: Error: Package:

[ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 07-11-2017 ] [ 004_basic_sanity.disk_operations ]

Hi, We have a failure in test 004_basic_sanity.disk_operations. >From the log I can see that vdsm has a KeyError: 'diskReplicate' and than reports the drive not found. Can you please check the issue? ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83641/* * Link to Job:

[ovirt-devel] [ OST Failure Report ] [ oVirt Master ] [ 05-12-2017 ] [ 006_migrations.migrate_vm ]

Hi, We had a failure for test 006_migrations.migrate_vm on master. There was a libvirt disruption in the migration src and after that vdsm reported the migration as failed because the vm already exists which makes me suspect a split bran case. The patch reported has nothing to do with this

[ovirt-devel] [ OST Failure Report ] [ oVirt Hosted-engine-ha Master ] [ 12-12-2017 ] [ 002_bootstrap.verify_add_hosts, 002_bootstrap.add_hosts ]

Hi, We had a failure on ovirt-hosted-engine-ha in two tests on bith basic and upgrade suite. Both tests failed on deploy host with the same missing package: python2-lxml ** *Link and headline of suspected patches: * ** * Patch reported as failed: https://gerrit.ovirt.org/#/c/85279/ - build:

[ovirt-devel] Fwd: [CQ]: 83325, 1 (ovirt-engine) failed "ovirt-4.1" system tests

Hi, We had a failure on ovirt-4.1 system tests. the failure is actually because of build artifacts job: http://jenkins.ovirt.org/job/ovirt-engine_4.1_build-artifacts-el7-x86_64/ which seems, was already fixed. Thanks, Dafna Forwarded Message Subject:[CQ]: 83325,1

[ovirt-devel] changeq failure due to vdsm build

Hi, I am seeing a failure in CQ (see below). this is because of failed job: ovirt-hosted-engine-ha_master_build-artifacts-fc26-x86_64 (28) failed building And this job seemed to have failed due to a packaging issue:

Re: [ovirt-devel] changeq failure due to ha build

sorry - forgot to change headline (there is also a failed vdsm build but not related to this failure). On 10/31/2017 03:22 PM, Dafna Ron wrote: > > Hi, > > I am seeing a failure in CQ (see below). > > this is because of failed job: > > ovirt-hosted-engine-ha_master_bui

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1] [ 31 Oct 2017 ] [ 002_bootstrap.add_dc ]

Hi, we had a failure in 002_bootstrap.add_dc in ovirt 4.1. I think that it's a dependency packaging issue for ruby-gem with the ovirt-host packages. ** *Link to suspected patches: https://gerrit.ovirt.org/#/c/83403/1* ** * Link to Job: *

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine-sdk) ] [ 27-04-2018 ] [ 004_basic_sanity.verify_vm_import ]

Hi, CQ reported a failure for test 004_basic_sanity.verify_vm_import on basic suite. It seems to me that its related to the reported change. can you please have a look? *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/89852/ -

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

Hi, We are failing on deploying engine (test: 001_upgrade_engine.test_initialize_engine) duet to version bump for package vdsm-jsonrpc. Can you please revert the change or add the missing package? Please note that all ovirt-engine changes are failing and there are a few. *Link and headline of

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

#/c/91081/ > > On Thu, May 10, 2018 at 3:19 PM, Martin Perina <mper...@redhat.com> wrote: > >> On Thu, May 10, 2018 at 1:55 PM, Dafna Ron <d...@redhat.com> wrote: >> >> > Hi, >> > >> > We are failing on deploying engine (test: 001_upgr

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (otopi+imgbased) ] [ 11-05-2018 ] [ 001_initialize_engine.test_initialize_engine ]

Hi, We are failing in 001_initialize_engine.test_initialize_engine in the upgrade suite. the issue seems to be related to ovn configuration. The changes reported by CQ are not the cause of this failure and I may be mistaken but I suspect it may be related to one of the below changes. *Link and

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

there anything new I need to do to make sure >> that the rpm is published? >> >> Thanks, >> Piotr >> >> [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_any_build-art >> ifacts-manual/55/ >> >> On Fri, May 11, 2018 at 12:20 PM, Dafna Ron <d...@re

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7522/console if it fails I will check why and we can take it from there Thanks, Dafna On Fri, May 11, 2018 at 3:33 PM, Martin Perina <mper...@redhat.com> wrote: > > > On Fri, May 11, 2018 at 2:17 PM, Dafna Ron <d...@redhat.com> wro

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

> that the rpm is published? > > Thanks, > Piotr > > [1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_any_build- > artifacts-manual/55/ > > On Fri, May 11, 2018 at 12:20 PM, Dafna Ron <d...@redhat.com> wrote: > >> Hi, >> >> This change is sti

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 10-05-2018 ] [ 001_upgrade_engine.test_initialize_engine ]

It is failing on the ovn issue which I reported today. I am following up and once the regression is solved I will re-run. On Fri, May 11, 2018 at 4:01 PM, Dafna Ron <d...@redhat.com> wrote: > yes, this is about the case. but you wanted to know why it takes a so long > to test a sing

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (otopi+imgbased) ] [ 11-05-2018 ] [ 001_initialize_engine.test_initialize_engine ]

:54 +0300 > Dafna Ron <d...@redhat.com> wrote: > > > Hi, > > > > We are failing in 001_initialize_engine.test_initialize_engine in the > > upgrade suite. > > the issue seems to be related to ovn configuration. > > > > The changes reported by CQ ar

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]

Eli, Martin - can you please take a look? Thanks, Dafna On Tue, May 22, 2018 at 7:09 PM, Dafna Ron <d...@redhat.com> wrote: > Hi, > > This failure seems to be related to the regression we found earlier today > which was causing failure in initialize engine: > https://gerri

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]

t.org/#/c/91586/ > > > On Wed, May 23, 2018 at 6:19 PM, Dafna Ron <d...@redhat.com> wrote: > >> ok. thank you for the update Martin. >> >> On Wed, May 23, 2018 at 4:16 PM, Martin Perina <mper...@redhat.com> >> wrote: >> >>> >>> >

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]

ok. thank you for the update Martin. On Wed, May 23, 2018 at 4:16 PM, Martin Perina <mper...@redhat.com> wrote: > > > On Wed, May 23, 2018 at 5:11 PM, Dafna Ron <d...@redhat.com> wrote: > >> Arik - any update? >> >> Thanks, >> Dafna >> &

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]

artin Perina <mper...@redhat.com> >> wrote: >> >>> >>> >>> On Wed, May 23, 2018 at 11:55 AM, Dafna Ron <d...@redhat.com> wrote: >>> >>>> Eli, Martin - can you please take a look? >>>> >>> >>> ​We have discu

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [22-05-2018 ] [ 004_basic_sanity.update_template_version]

Hi, This failure seems to be related to the regression we found earlier today which was causing failure in initialize engine: https://gerrit.ovirt.org/#/c/89293/ - core:make search string fields not null and empty The fix for the above change was reported as failed on the update template test

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

Thanks Eli. On Wed, Jun 6, 2018 at 10:49 AM, Eli Mesika wrote: > Hi Dafna > > We are aware of that, the patch will be merged upstream ASAP and I sent a > 4.2 patch as well , hope to have both merge soon > > On Wed, Jun 6, 2018 at 11:45 AM, Dafna Ron wrote: > >

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

Hi Martin, Eli and Arik. can you please give an update on this? Is there a bug reported for this? Thanks, Danfa On Fri, Jun 8, 2018 at 1:26 PM, Martin Perina wrote: > > > On Fri, Jun 8, 2018 at 12:56 PM, Dafna Ron wrote: > >> Hi Martin, Eli, >> >> It seems

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (vdsm) ] [ 12-06-2018 ] [ 004_basic_sanity.preview_snapshot_with_memory ]

Hi, We have a failure in 004_basic_sanity.preview_snapshot_with_memory on master suite. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/90532/ - * *vm: Do not remove replicate attribute if abort failedLink to Job:*

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

Hi Martin, Eli, It seems the fix has failed on the same test: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue-tester/8068/ can you please have a look? Thanks, Dafna On Wed, Jun 6, 2018 at 11:03 AM, Dafna Ron wrote: > Thanks Eli. > > On Wed, Ju

[ovirt-devel] Re: [ OST Failure Report ] [ oVirt Master (vdsm) ] [ 12-06-2018 ] [ 004_basic_sanity.preview_snapshot_with_memory ]

Benny check the issue, and we also had a vdsm build that passed so it seems that there may be a race in the test that cause this failure. We'll investigate the race. here is the ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 On Tue, Jun 12, 2018 at 1:29 PM, Dafna Ron wrote: >

  1   2   3   4   5   >