Re: [ovirt-devel] oVirt 4.2.0 blockers review - Day 2

2017-11-29 Thread Yaniv Kaul
On Wed, Nov 29, 2017 at 9:40 AM, Sandro Bonazzola wrote: > Hi, > we had 7 blockers yesterday and the list is now down to 4: > (It'll be easier to review with hyperlinks) > Bug ID Product Assignee Status Summary Changed > 1516113 cockpit-ovirt phbai...@redhat.com POST

Re: [ovirt-devel] oVirt 4.2.0 blockers review - Day 2

2017-11-29 Thread Ala Hino
On Wed, Nov 29, 2017 at 10:09 AM, Yaniv Kaul wrote: > > > On Wed, Nov 29, 2017 at 9:40 AM, Sandro Bonazzola > wrote: > >> Hi, >> we had 7 blockers yesterday and the list is now down to 4: >> > > (It'll be easier to review with hyperlinks) > > >> Bug ID

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Dan Kenigsberg
On Tue, Nov 28, 2017 at 10:29 PM, Michal Skrivanek wrote: > >> On 28 Nov 2017, at 15:17, Dan Kenigsberg wrote: >> >> >> >> On Tue, Nov 28, 2017 at 9:54 PM, Michal Skrivanek >> wrote: >> >>> On 28 Nov 2017, at 06:36,

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Martin Perina
On Wed, Nov 29, 2017 at 12:37 AM, Maor Lipchuk wrote: > > > On Wed, Nov 29, 2017 at 12:23 AM, Piotr Kliczewski > wrote: > >> >> >> On Tue, Nov 28, 2017 at 10:26 PM, Martin Perina >> wrote: >> >>> >>> >>> On Tue, Nov 28, 2017 at

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

2017-11-29 Thread Nir Soffer
Do we have more info from Didi's debug plugin now? On Wed, Nov 29, 2017 at 12:07 PM Dafna Ron wrote: > *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

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

2017-11-29 Thread Dafna Ron
this is the plugin info from steup log but I don't see anything more than we have seen except a timeout. https://pastebin.com/QVtNRNWV

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

2017-11-29 Thread Yedidyah Bar David
On Wed, Nov 29, 2017 at 1:00 PM, Dafna Ron wrote: > this is the plugin info from steup log but I don't see anything more than > we have seen except a timeout. > > https://pastebin.com/QVtNRNWV > > http://jenkins.ovirt.org/job/ovirt-master_change-queue- >

Re: [ovirt-devel] oVirt 4.2.0 blockers review - Day 2

2017-11-29 Thread Yaniv Kaul
On Wed, Nov 29, 2017 at 10:30 AM, Ala Hino wrote: > > > On Wed, Nov 29, 2017 at 10:09 AM, Yaniv Kaul wrote: > >> >> >> On Wed, Nov 29, 2017 at 9:40 AM, Sandro Bonazzola >> wrote: >> >>> Hi, >>> we had 7 blockers yesterday and the list is

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Arik Hadas
On Tue, Nov 28, 2017 at 10:29 PM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > > > On 28 Nov 2017, at 15:17, Dan Kenigsberg wrote: > > > > > > > > On Tue, Nov 28, 2017 at 9:54 PM, Michal Skrivanek < > michal.skriva...@redhat.com> wrote: > > > >> On 28 Nov 2017, at

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

2017-11-29 Thread Yedidyah Bar David
On Wed, Nov 29, 2017 at 12:18 PM, Nir Soffer wrote: > Do we have more info from Didi's debug plugin now? > Not yet. Patch to install the debug plugins was merged this morning, build below failed yesterday evening. > > On Wed, Nov 29, 2017 at 12:07 PM Dafna Ron

Re: [ovirt-devel] oVirt 4.2.0 blockers review - Day 2

2017-11-29 Thread Ala Hino
In the engine log of the OST that I run on the patch I don't see the error seen before. Waiting for final confirmation from Raz. On Wed, Nov 29, 2017 at 10:53 AM, Yaniv Kaul wrote: > > > On Wed, Nov 29, 2017 at 10:30 AM, Ala Hino wrote: > >> >> >> On Wed,

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

2017-11-29 Thread Dafna Ron
* 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] oVirt 4.2.0 blockers review

2017-11-29 Thread Ala Hino
Fix verified by the automation and will be merged soon. On Tue, Nov 28, 2017 at 6:35 PM, Ala Hino wrote: > Issue analyzed and fix verified by the automation test case. > Now, running all merge related automation test cases to make sure no > regression/new issues introduced. >

[ovirt-devel] please test UI plugins in 4.2 beta

2017-11-29 Thread Greg Sheremeta
Hi everyone, [I should have sent this message sooner -- apologies, and thanks to Martin Sivak for the reminder!] If you're trying out oVirt 4.2 Beta, please check that any existing UI plugins [1] you are using 1. still work (they should!), and 2. look good in the new UI. If something doesn't

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

2017-11-29 Thread Dafna Ron
we had a failure on 002_bootstrap.verify_add_hosts but the error is on imageio I looked at the host log that Nir added and I can only see that the address is in use which seems to be the same issue we have in initialize engine.

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Martin Sivak
Hi, I think I found one issue.. I do not see the extra menu items that were supposed to be added to VMs (used to be available in context menu as well). You can check it with http://jenkins.ovirt.org/job/ovirt-optimizer_master_check-patch-el7-x86_64/65/ Martin On Wed, Nov 29, 2017 at 1:22 AM,

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Nir Soffer
On Wed, Nov 29, 2017 at 9:22 AM Yaniv Kaul wrote: > On Wed, Nov 29, 2017 at 12:10 AM, Nir Soffer wrote: > >> We merge the last multipath alerts patches today. >> > > But engine side is not ready, so the feature is not yet usable. > The main work is the

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Greg Sheremeta
+Alexander, can you take a look? On Wed, Nov 29, 2017 at 8:33 AM, Martin Sivak wrote: > Hi, > > I think I found one issue.. I do not see the extra menu items that were > supposed to be added to VMs (used to be available in context menu as well). > > You can check it with > >

Re: [ovirt-devel] oVirt 4.2.0 blockers review - Day 2

2017-11-29 Thread Dan Kenigsberg
On Wed, Nov 29, 2017 at 9:40 AM, Sandro Bonazzola wrote: > Hi, > we had 7 blockers yesterday and the list is now down to 4: > Bug ID Product Assignee Status Summary Changed > 1516113 cockpit-ovirt phbai...@redhat.com POST Deploy the HostedEngine > failed with the default CPU

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Alexander Wels
On Wednesday, November 29, 2017 10:16:27 AM EST Martin Sivak wrote: > Thanks to you too for checking. > > Martin > Fix is pending review [1]. We moved the main views to a different class hierarchy and it wasn't inheriting the methods to add the buttons. Alexander [1]

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

2017-11-29 Thread Yedidyah Bar David
On Wed, Nov 29, 2017 at 3:56 PM, Dafna Ron wrote: > we had a failure on 002_bootstrap.verify_add_hosts but the error is on > imageio > > I looked at the host log that Nir added and I can only see that the > address is in use which seems to be the same issue we have in initialize

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Martin Sivak
I will try finding time tomorrow. Thanks. Martin On Wed, Nov 29, 2017 at 6:02 PM, Greg Sheremeta wrote: > Martin, we've merged the fix. (Thanks to Alexander for the super fast fix.) > > Care to test with master? > > On Wed, Nov 29, 2017 at 10:50 AM, Alexander Wels

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Simone Tiraboschi
I think that this one should be considered a blocker as well: https://bugzilla.redhat.com/show_bug.cgi?id=1518887 - ovirt-ha-agent fails parsing the OVF_STORE On Wed, Nov 29, 2017 at 2:20 PM, Ala Hino wrote: > Fix verified by the automation and will be merged soon. > > On

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Greg Sheremeta
Martin, we've merged the fix. (Thanks to Alexander for the super fast fix.) Care to test with master? On Wed, Nov 29, 2017 at 10:50 AM, Alexander Wels wrote: > On Wednesday, November 29, 2017 10:16:27 AM EST Martin Sivak wrote: > > Thanks to you too for checking. > > > >

Re: [ovirt-devel] oVirt 4.2 and UI plugin infrastructure

2017-11-29 Thread Greg Sheremeta
Discussed with Alexander, and yep this is an issue. I opened https://bugzilla.redhat.com/show_bug.cgi?id=1518724 Thanks for checking and reporting! On Wed, Nov 29, 2017 at 8:35 AM, Greg Sheremeta wrote: > +Alexander, can you take a look? > > On Wed, Nov 29, 2017 at 8:33

[ovirt-devel] [OST Failure] [oVirt Master] [HC] Hosted engine fails to install

2017-11-29 Thread Sahina Bose
Hi, The error with HE install is : Starting vdsmd", "[ ERROR ] Failed to execute stage 'Misc configuration': Couldn't connect to VDSM within 15 seconds". Is there a configuration parameter that needs to be set to change the timeout, or is this a bug? Logs at :

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Dan Kenigsberg
On Wed, Nov 29, 2017 at 7:33 PM, Simone Tiraboschi wrote: > I think that this one should be considered a blocker as well: > https://bugzilla.redhat.com/show_bug.cgi?id=1518887 - ovirt-ha-agent > fails parsing the OVF_STORE > Ouch, the code should now accept both URI, to

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Martin Sivak
> Ouch, the code should now accept both URI, to support OVFs created prior to > the change, as well as new ones. Yeah, we will have to add some detection of the used URI. The library does not support wildcards I am afraid. Martin On Wed, Nov 29, 2017 at 8:43 PM, Dan Kenigsberg

Re: [ovirt-devel] oVirt 4.2.0 blockers review

2017-11-29 Thread Michal Skrivanek
> On 29 Nov 2017, at 15:24, Martin Sivak wrote: > >> Ouch, the code should now accept both URI, to support OVFs created prior to >> the change, as well as new ones. > > Yeah, we will have to add some detection of the used URI. The library > does not support wildcards I am