Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

The patch was reported to cause 3 different issues but I cannot say for sure that the notifier error was actually one of them. I can say that all issues from master and 4.2 were cleared once the fix from Shmuel was merged and tested in cq. On Wed, Mar 21, 2018 at 10:28 AM, Michal Skrivanek <

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

> On 20 Mar 2018, at 10:33, Yaniv Kaul wrote: > > > > On Tue, Mar 20, 2018 at 9:49 AM, Michal Skrivanek > > wrote: > I’m not sure what is that test actually testing, if it depends on the > previous host

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

On Tue, Mar 20, 2018 at 9:49 AM, Michal Skrivanek < michal.skriva...@redhat.com> wrote: > I’m not sure what is that test actually testing, if it depends on the > previous host action which fails but is not verified it still may be > relevant to Shmuel’s patch > adding author of the test and the

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

I’m not sure what is that test actually testing, if it depends on the previous host action which fails but is not verified it still may be relevant to Shmuel’s patch adding author of the test and the notifier owner > On 19 Mar 2018, at 13:06, Dafna Ron wrote: > > Hi, > > We

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (Ovirt-ngine) ] [ 19-03-2018 ] [ 002_bootstrap.verify_notifier ]

Hi, We had a failure in test 002_bootstrap.verify_notifier. I can't see anything wrong with the notifier and I don't think it should be related to the change that was reported. the test itself is looking for vdc_stop in messages which I do not indeed see but I am not sure what is the cause and