[ovirt-devel] Re: OST on Stream

On 22. 1. 2021, at 13:01, Marcin Sobczyk <msobczyk(a)redhat.com&gt; wrote: On 1/22/21 12:00 PM, Marcin Sobczyk wrote: > Hi > > On 1/22/21 11:45 AM, Michal Skrivanek wrote: >> There seems to be multiple issues really >> >> 1) First it fails on “unknown state” of ovirt-engine-notifier service. Seems the OST code is not handling service states well and just explodes >> 2) Either way, the problem is it's stopped. It should be running >> 3) if you start it manually it gets to the engine-config test and restarts engine. It explodes here again, apparently same reason as #1 >> 4) host installation fails - didi’s https://gerrit.ovirt.org/#/c/ovirt-engine/+/113101/ is fixing it >> 5) verify_engine_notifier fails when we try to stop it. it’s not running due to #2 and it explodes anyway due to #1 >> >> rest seems to work fine except few more #1 issues, so that’s good… >> >> Marcin, can you please prioritize #1? > Sure, looking... This is a known issue. Bugs that have been filed for this: https://bugzilla.redhat.com/show_bug.cgi?id=1908275 https://bugzilla.redhat.com/show_bug.cgi?id=1901449 There's also a workaround made for ansible modules: https://github.com/ansible/ansible/issues/71528 I actually cannot reproduce this issue on my CentOS 8.3 servers. I think the problem is that CI agents are based on RHEL 8.2, which has the unpatched ansible version.

Regards, Marcin > >> Martin, any idea about notifier? >> >> Thanks, >> michal >>