On Tue, Feb 19, 2019 at 10:34 AM Doron Fediuck <dfediuck(a)redhat.com> wrote:
On Tue, 19 Feb 2019 at 10:25, Yedidyah Bar David <didi(a)redhat.com> wrote:
> On Tue, Feb 19, 2019 at 9:52 AM Yedidyah Bar David <didi(a)redhat.com>
> wrote:
>
>> On Tue, Feb 19, 2019 at 9:49 AM Eyal Edri <eedri(a)redhat.com> wrote:
>>
>>>
>>>
>>> On Tue, Feb 19, 2019 at 9:29 AM Yedidyah Bar David <didi(a)redhat.com>
>>> wrote:
>>>
>>>> On Tue, Feb 19, 2019 at 9:15 AM Dan Kenigsberg <danken(a)redhat.com>
>>>> wrote:
>>>> >
>>>> > On Mon, Feb 18, 2019 at 11:39 AM Martin Perina
<mperina(a)redhat.com>
>>>> wrote:
>>>> > >
>>>> > >
>>>> > >
>>>> > > On Mon, Feb 18, 2019 at 10:32 AM Dafna Ron
<dron(a)redhat.com>
>>>> wrote:
>>>> > >>
>>>> > >> Also, try to run the same in mock which would isolate your
>>>> environment
>>>> > >
>>>> > >
>>>> > > My environment is minimal CentOS 7 VM installed from scratch,
why
>>>> would mock help me?
>>>> > >
>>>> > > Unfortunately I have FC29 on laptop and I haven't been able
to run
>>>> OST on it so far :-(
>>>> > >
>>>> > > I have been discussing with Galit over IRC and so far we
haven't
>>>> been able to identify any different package version on my CentOS (where
>>>> everything works as expected) and her OST environment (where PG 9.5
failed
>>>> to start).
>>>> >
>>>> >
>>>> > Have you tried running OST 4.2 locally? When it fails, it should
keep
>>>> > everything available for you to ssh into.
>>>> > It has been the 4th night that the out 4.2 suite is failing, which
is
>>>> > not a healthy condition to be in.
>>>>
>>>> Reproduced and added this comment:
>>>>
>>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1518599#c6
>>>>
>>>> If we do not get a solution soon, we can consider a workaround (as we
>>>> did in bug 1518253).
>>>>
>>>
>>> Galit sent a WA which seems to work, do we want to merge it? [1]
>>>
>>
>> Current version of this patch is only for the upgrade suites. I do not
>> object to merging, we might want to handle somewhere for all suites.
>>
>> I am working on a workaround in engine-setup.
>>
>
> Seems like it would not be so easy, so perhaps for now we can update our
> images in CI to make sure they already have latest selinux packages. I
> think this will fix too.
>
So is this an selinux policy bug? Or is it on our side?
It's a bug in the selinux policy package, yes, not on our side.
Now pushed a workaround:
>
>>
>>
>>> or maybe consider reverting the vmconsole patch? [2] which might have
>>> started this whole issue?
>>>
>>
>> I think it's not related, not sure.
>>
>>
>>>
>>>
>>> [1]
https://gerrit.ovirt.org/#/c/97843/
>>> [2]
https://gerrit.ovirt.org/#/c/97704/
>>>
>>>
>>>>
>>>> Best regards,
>>>> --
>>>> Didi
>>>> _______________________________________________
>>>> Devel mailing list -- devel(a)ovirt.org
>>>> To unsubscribe send an email to devel-leave(a)ovirt.org
>>>> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
>>>> oVirt Code of Conduct:
>>>>
https://www.ovirt.org/community/about/community-guidelines/
>>>> List Archives:
>>>>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XYD4CJQGHAU...
>>>>
>>>
>>>
>>> --
>>>
>>> Eyal edri
>>>
>>>
>>> MANAGER
>>>
>>> RHV/CNV DevOps
>>>
>>> EMEA VIRTUALIZATION R&D
>>>
>>>
>>> Red Hat EMEA <
https://www.redhat.com/>
>>> <
https://red.ht/sig> TRIED. TESTED. TRUSTED.
>>> <
https://redhat.com/trusted>
>>> phone: +972-9-7692018
>>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>
>>
>>
>> --
>> Didi
>>
>
>
> --
> Didi
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/7QF4RSTMYHZ...
>