Re: [ovirt-devel] [kubevirt-dev] Re: [virt-tools-list] Project for profiles and defaults for libvirt domains

[resending to include KubeVirt devs ] YANIV LAVI SENIOR TECHNICAL PRODUCT MANAGER Red Hat Israel Ltd. 34 Jerusalem Road, Building A, 1st floor Ra'anana, Israel 4350109 yl...@redhat.comT: +972-9-7692306/8272306 F: +972-9-7692223IM: ylavi

Re: [ovirt-devel] [kubevirt-dev] Re: [virt-tools-list] Project for profiles and defaults for libvirt domains

Hi, I'd like to go one step back and discuss why we should try to do this on the high level. For the last 5-10 years of KVM development, we are pragmatically providing the Linux host level APIs via project specific host agents/integration code (Nova agent, oVirt host agent, virt-manager). In

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

Re: [ovirt-devel] [OST][HC] HE fails to deploy

On Tue, Apr 3, 2018 at 1:50 PM, Simone Tiraboschi wrote: > > > On Tue, Apr 3, 2018 at 10:14 AM, Simone Tiraboschi > wrote: > >> >> >> On Mon, Apr 2, 2018 at 4:44 PM, Sahina Bose wrote: >> >>> HE fails to deploy at waiting for host to

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

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 domain This seems to happen multiple times sporadically, I thought this would be

Re: [ovirt-devel] [vdsm][ci] EL7 failing for timeout lately

Adding infra, from infra side I'm not aware of any major changes that can cause this to happen. Have you considered introducing performance testing so you'll know how much time each test take and fail/warn if it start to take much longer? On Wed, Apr 4, 2018 at 3:35 PM, Francesco Romani

[ovirt-devel] [vdsm][ci] EL7 failing for timeout lately

Hi all, in the last few days quite a lot of CI tests on LE7 workers failed for timeout. Random example: http://jenkins.ovirt.org/job/vdsm_4.2_check-patch-el7-x86_64/246/consoleFull This happened both on 4.2 and on master test suite, quite often but not always. I wonder if we should just

Re: [ovirt-devel] oVirt log analyzer

Piotr Kliczewski writes: > On Wed, Apr 4, 2018 at 10:47 AM, Milan Zamazal wrote: >> Barak Korren writes: >> > >>> Right now, when a test fails in OST - al you get is the traceback from >>> nose of the oVirt API cll you've

Re: [ovirt-devel] oVirt log analyzer

On Wed, Apr 4, 2018 at 10:47 AM, Milan Zamazal wrote: > Barak Korren writes: > >> Right now, when a test fails in OST - al you get is the traceback from >> nose of the oVirt API cll you've made. For some tests additional >> information is provided by

Re: [ovirt-devel] oVirt log analyzer

Barak Korren writes: > Right now, when a test fails in OST - al you get is the traceback from > nose of the oVirt API cll you've made. For some tests additional > information is provided by having nise collect it from STDOUT. > > It could be very useful if we could use some

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

On 3 April 2018 at 17:43, Dan Kenigsberg wrote: > On Tue, Apr 3, 2018 at 3:57 PM, Piotr Kliczewski wrote: >> Dan, >> >> It looks like it was one of the calls triggered when vdsm was down: >> >> 2018-04-03 05:30:16,065-0400 INFO (mailbox-hsm) >>