Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 25, 2018 at 7:20 PM, Ravi Shankar Nori wrote: > > > On Wed, Apr 25, 2018 at 10:57 AM, Martin Perina wrote: >> >> >> >> On Tue, Apr 24, 2018 at 3:28 PM, Dan Kenigsberg wrote: >>> >>> On Tue, Apr 24, 2018 at 4:17 PM, Ravi

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 25, 2018 at 8:15 PM, Piotr Kliczewski wrote: > > > śr., 25 kwi 2018, 19:07 użytkownik Martin Perina > napisał: >> >> Ravi/Piotr, so what's the connection between non-blocking threads, >> jsonrpc-java connection closing and failing this network

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

śr., 25 kwi 2018, 19:07 użytkownik Martin Perina napisał: > Ravi/Piotr, so what's the connection between non-blocking threads, > jsonrpc-java connection closing and failing this network test? Does it mean > that non-blocking threads change just revealed the jsonrpc-java issue

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Ravi/Piotr, so what's the connection between non-blocking threads, jsonrpc-java connection closing and failing this network test? Does it mean that non-blocking threads change just revealed the jsonrpc-java issue which we haven't noticed before? And did the test really works with code prior to

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 25, 2018 at 10:57 AM, Martin Perina wrote: > > > On Tue, Apr 24, 2018 at 3:28 PM, Dan Kenigsberg wrote: > >> On Tue, Apr 24, 2018 at 4:17 PM, Ravi Shankar Nori >> wrote: >> > >> > >> > On Tue, Apr 24, 2018 at 7:00 AM, Dan

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 25, 2018 at 5:57 PM, Martin Perina wrote: > > > On Tue, Apr 24, 2018 at 3:28 PM, Dan Kenigsberg wrote: >> >> On Tue, Apr 24, 2018 at 4:17 PM, Ravi Shankar Nori >> wrote: >> > >> > >> > On Tue, Apr 24, 2018 at 7:00 AM, Dan

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 10:27 PM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 10:46 AM, Ravi Shankar Nori > wrote: >> >> >> >> On Tue, Apr 24, 2018 at 10:29 AM, Dan Kenigsberg >> wrote: >>> >>> On Tue, Apr 24, 2018 at 5:09 PM,

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 10:46 AM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 10:29 AM, Dan Kenigsberg > wrote: > >> On Tue, Apr 24, 2018 at 5:09 PM, Ravi Shankar Nori >> wrote: >> > >> > >> > On Tue, Apr 24, 2018 at 9:47 AM,

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 10:29 AM, Dan Kenigsberg wrote: > On Tue, Apr 24, 2018 at 5:09 PM, Ravi Shankar Nori > wrote: > > > > > > On Tue, Apr 24, 2018 at 9:47 AM, Dan Kenigsberg > wrote: > >> > >> On Tue, Apr 24, 2018 at 4:36 PM, Ravi

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 5:09 PM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 9:47 AM, Dan Kenigsberg wrote: >> >> On Tue, Apr 24, 2018 at 4:36 PM, Ravi Shankar Nori >> wrote: >> > >> > >> > On Tue, Apr 24, 2018 at 9:24 AM, Martin

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 9:47 AM, Dan Kenigsberg wrote: > On Tue, Apr 24, 2018 at 4:36 PM, Ravi Shankar Nori > wrote: > > > > > > On Tue, Apr 24, 2018 at 9:24 AM, Martin Perina > wrote: > >> > >> > >> > >> On Tue, Apr 24, 2018 at 3:17 PM,

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 4:36 PM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 9:24 AM, Martin Perina wrote: >> >> >> >> On Tue, Apr 24, 2018 at 3:17 PM, Ravi Shankar Nori >> wrote: >>> >>> >>> >>> On Tue, Apr 24, 2018 at 7:00 AM,

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 9:24 AM, Martin Perina wrote: > > > On Tue, Apr 24, 2018 at 3:17 PM, Ravi Shankar Nori > wrote: > >> >> >> On Tue, Apr 24, 2018 at 7:00 AM, Dan Kenigsberg >> wrote: >> >>> Ravi's patch is in, but a similar problem

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 4:17 PM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 7:00 AM, Dan Kenigsberg wrote: >> >> Ravi's patch is in, but a similar problem remains, and the test cannot >> be put back into its place. >> >> It seems that while Vdsm

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 3:17 PM, Ravi Shankar Nori wrote: > > > On Tue, Apr 24, 2018 at 7:00 AM, Dan Kenigsberg wrote: > >> Ravi's patch is in, but a similar problem remains, and the test cannot >> be put back into its place. >> >> It seems that while Vdsm

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 7:00 AM, Dan Kenigsberg wrote: > Ravi's patch is in, but a similar problem remains, and the test cannot > be put back into its place. > > It seems that while Vdsm was taken down, a couple of getCapsAsync > requests queued up. At one point, the host

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 3:14 PM, Yaniv Kaul wrote: > > > On Tue, Apr 24, 2018 at 2:00 PM, Dan Kenigsberg wrote: >> >> Ravi's patch is in, but a similar problem remains, and the test cannot >> be put back into its place. >> >> It seems that while Vdsm was

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 24, 2018 at 2:00 PM, Dan Kenigsberg wrote: > Ravi's patch is in, but a similar problem remains, and the test cannot > be put back into its place. > > It seems that while Vdsm was taken down, a couple of getCapsAsync > - Why is VDSM down? Y. > requests queued up.

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Ravi's patch is in, but a similar problem remains, and the test cannot be put back into its place. It seems that while Vdsm was taken down, a couple of getCapsAsync requests queued up. At one point, the host resumed its connection, before the requests have been cleared of the queue. After the

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

> On 12 Apr 2018, at 17:15, Dafna Ron wrote: > > hi, > > we are failing randomly on test 006_migrations.migrate_vm with what seems to > be the same issue. > > the vm seems to be migrated successfully but engine thinks that it failed and > re-calls migration getting a

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

hi, we are failing randomly on test 006_migrations.migrate_vm with what seems to be the same issue. the vm seems to be migrated successfully but engine thinks that it failed and re-calls migration getting a response of vm already exists. I don't think this is an issue with the test but rather a

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Arik Hadas writes: > On Wed, Apr 11, 2018 at 12:45 PM, Alona Kaplan wrote: > >> >> >> On Tue, Apr 10, 2018 at 6:52 PM, Gal Ben Haim wrote: >> >>> I'm seeing the same error in [1], during 006_migrations.migrate_vm. >>> >>> [1]

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 11, 2018 at 12:45 PM, Alona Kaplan wrote: > > > On Tue, Apr 10, 2018 at 6:52 PM, Gal Ben Haim wrote: > >> I'm seeing the same error in [1], during 006_migrations.migrate_vm. >> >> [1]

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Tue, Apr 10, 2018 at 6:52 PM, Gal Ben Haim wrote: > I'm seeing the same error in [1], during 006_migrations.migrate_vm. > > [1] http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1650/ > Seems like another bug. The migration failed since for some reason the vm is

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Hi Ravi, Added comments to the patch. Regarding the lock - the lock shouldn't be released until the command and its callbacks were finished. The treatment of a delayed failure should be under lock since it doesn't make sense to take care of the failure while other monitoring process is possibly

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

This [1] should fix the multiple release lock issue [1] https://gerrit.ovirt.org/#/c/90077/ On Tue, Apr 10, 2018 at 3:53 PM, Ravi Shankar Nori wrote: > Working on a patch will post a fix > > Thanks > > Ravi > > On Tue, Apr 10, 2018 at 9:14 AM, Alona Kaplan

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Working on a patch will post a fix Thanks Ravi On Tue, Apr 10, 2018 at 9:14 AM, Alona Kaplan wrote: > Hi all, > > Looking at the log it seems that the new GetCapabilitiesAsync is > responsible for the mess. > > - > * 08:29:47 - engine loses connectivity to host

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

I'm seeing the same error in [1], during 006_migrations.migrate_vm. [1] http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1650/ On Tue, Apr 10, 2018 at 4:14 PM, Alona Kaplan wrote: > Hi all, > > Looking at the log it seems that the new GetCapabilitiesAsync is >

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Hi all, Looking at the log it seems that the new GetCapabilitiesAsync is responsible for the mess. - * 08:29:47 - engine loses connectivity to host 'lago-basic-suite-4-2-host-0'.* *- Every 3 seconds a getCapabalititiesAsync request is sent to the host (unsuccessfully).* * before each

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Sun, Apr 8, 2018 at 9:21 AM, Edward Haas wrote: > > > On Sun, Apr 8, 2018 at 9:15 AM, Eyal Edri wrote: > >> Was already done by Yaniv - https://gerrit.ovirt.org/#/c/89851. >> Is it still failing? >> >> On Sun, Apr 8, 2018 at 8:59 AM, Barak Korren

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Sun, Apr 8, 2018 at 9:15 AM, Eyal Edri wrote: > Was already done by Yaniv - https://gerrit.ovirt.org/#/c/89851. > Is it still failing? > > On Sun, Apr 8, 2018 at 8:59 AM, Barak Korren wrote: > >> On 7 April 2018 at 00:30, Dan Kenigsberg

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Was already done by Yaniv - https://gerrit.ovirt.org/#/c/89851. Is it still failing? On Sun, Apr 8, 2018 at 8:59 AM, Barak Korren wrote: > On 7 April 2018 at 00:30, Dan Kenigsberg wrote: > > No, I am afraid that we have not managed to understand why

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On 7 April 2018 at 00:30, Dan Kenigsberg wrote: > No, I am afraid that we have not managed to understand why setting and > ipv6 address too the host off the grid. We shall continue researching > this next week. > > Edy, https://gerrit.ovirt.org/#/c/88637/ is already 4 weeks

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

No, I am afraid that we have not managed to understand why setting and ipv6 address too the host off the grid. We shall continue researching this next week. Edy, https://gerrit.ovirt.org/#/c/88637/ is already 4 weeks old, but could it possibly be related (I really doubt that)? On Fri, Apr 6,

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

Dan, was there a fix for the issues? can I have a link to the fix if there was? Thanks, Dafna On Wed, Apr 4, 2018 at 5:01 PM, Gal Ben Haim wrote: > From lago's log, I see that lago collected the logs from the VMs using ssh > (after the test failed), which means > that the

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

>From lago's log, I see that lago collected the logs from the VMs using ssh (after the test failed), which means that the VM didn't crash. On Wed, Apr 4, 2018 at 5:27 PM, Dan Kenigsberg wrote: > On Wed, Apr 4, 2018 at 4:59 PM, Barak Korren wrote: > > Test

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-04 ] [006_migrations.prepare_migration_attachments_ipv6]

On Wed, Apr 4, 2018 at 4:59 PM, Barak Korren wrote: > Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ] > > Link to suspected patches: > (Probably unrelated) > https://gerrit.ovirt.org/#/c/89812/1 (ovirt-engine-sdk) - examples: > export template to an export