For building the centos/rhel images I'm using the information from this
document

https://docs.google.com/document/d/1fxXBcgHnQr3r2qrSzXiSlpNMMLWnbq899s8rUP38KHw/edit?usp=sharing


On Wed, Feb 20, 2019 at 11:29 AM Yedidyah Bar David <d...@redhat.com> wrote:

> On Tue, Feb 19, 2019 at 8:51 PM Anton Marchukov <amarc...@redhat.com>
> wrote:
>
>> I think having the new base image working confirms the assumption that
>> the problem was related to some old selinux package.
>>
>
> How are the images built? I searched a bit and found [1]. Do we run it
> manually? In jenkins? Elsewhere? Do we keep logs? To investigate deeper,
> I'd like to understand how exactly we built the broken images.
>
> [1] https://github.com/lago-project/lago-images
>
>
>> Then we just need to estimate the probability of users having those
>> package installed and not upgraded?
>>
>
> Not very probable, AFAICT. I *think* the flow is something like this, but
> this is not more than a (not-so-)wild guess:
>
> 1. Install el 7.2 (with selinux-policy 3.12)
> 2. Upgrade to later
> 3. Reboot the machine without a working /dev/console
> 4. Install scl pg and initdb
>
> (1.) or (2.) might be about how we create the images, (3.) might be
> specific to libvirt/lago.
>
>
>> Anton.
>>
>> On Tue, Feb 19, 2019 at 7:47 PM Martin Perina <mper...@redhat.com> wrote:
>>
>>>
>>>
>>> On Tue, 19 Feb 2019, 19:22 Eyal Edri <ee...@redhat.com wrote:
>>>
>>>>
>>>>
>>>> On Tue, Feb 19, 2019, 19:45 Galit Rosenthal <grose...@redhat.com wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> U/S CQ master passed after the use of an updated image
>>>>>
>>>>
>>>> +1, glad to hear that.
>>>> are we going to apply also the other suggestion for workarounds for
>>>> postgresql or abandon them?
>>>>
>>>
>>> I'd say let's use updated image to unblock OST, we discus further
>>> improvements later...
>>>
>>>
>>>>
>>>>> Regards
>>>>> Galit
>>>>>
>>>>>
>>>>>
>>>>> בתאריך יום ג׳, 19 בפבר׳ 2019, 17:25, מאת Sandro Bonazzola <
>>>>> sbona...@redhat.com>:
>>>>>
>>>>>>
>>>>>>
>>>>>> Il giorno mar 19 feb 2019 alle ore 10:53 Anton Marchukov <
>>>>>> amarc...@redhat.com> ha scritto:
>>>>>>
>>>>>>> Hello Tal, Sandro.
>>>>>>>
>>>>>>> Since engine from previous tag was failing and hence it is not yet
>>>>>>> build we might consider including this fix into the new tag that we 
>>>>>>> need to
>>>>>>> do anyway (in case the bumps are not merged yet).
>>>>>>>
>>>>>>
>>>>>> I'm trying to verify didi's patch, but it's kind of hard to reproduce
>>>>>> on my laptop.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Anton.
>>>>>>>
>>>>>>> > On 19 Feb 2019, at 10:40, Yedidyah Bar David <d...@redhat.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > On Tue, Feb 19, 2019 at 10:34 AM Doron Fediuck <
>>>>>>> dfedi...@redhat.com> wrote:
>>>>>>> >
>>>>>>> >
>>>>>>> > On Tue, 19 Feb 2019 at 10:25, Yedidyah Bar David <d...@redhat.com>
>>>>>>> wrote:
>>>>>>> > On Tue, Feb 19, 2019 at 9:52 AM Yedidyah Bar David <
>>>>>>> d...@redhat.com> wrote:
>>>>>>> > On Tue, Feb 19, 2019 at 9:49 AM Eyal Edri <ee...@redhat.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> >
>>>>>>> > On Tue, Feb 19, 2019 at 9:29 AM Yedidyah Bar David <
>>>>>>> d...@redhat.com> wrote:
>>>>>>> > On Tue, Feb 19, 2019 at 9:15 AM Dan Kenigsberg <dan...@redhat.com>
>>>>>>> wrote:
>>>>>>> > >
>>>>>>> > > On Mon, Feb 18, 2019 at 11:39 AM Martin Perina <
>>>>>>> mper...@redhat.com> wrote:
>>>>>>> > > >
>>>>>>> > > >
>>>>>>> > > >
>>>>>>> > > > On Mon, Feb 18, 2019 at 10:32 AM Dafna Ron <d...@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:
>>>>>>> >
>>>>>>> > https://gerrit.ovirt.org/97870
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > 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@ovirt.org
>>>>>>> > To unsubscribe send an email to devel-le...@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/XYD4CJQGHAUKDQ43QY44D3FH6HA3ET4L/
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > EYAL EDRI
>>>>>>> >
>>>>>>> > MANAGER
>>>>>>> > RHV/CNV DEVOPS
>>>>>>> > EMEA VIRTUALIZATION R&D
>>>>>>> >
>>>>>>> > Red Hat EMEA
>>>>>>> >       TRIED. TESTED. TRUSTED.
>>>>>>> > phone: +972-9-7692018
>>>>>>> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Didi
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Didi
>>>>>>> > _______________________________________________
>>>>>>> > Devel mailing list -- devel@ovirt.org
>>>>>>> > To unsubscribe send an email to devel-le...@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/7QF4RSTMYHZYIX6QDLHT7NYVMR5UEVPW/
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > Didi
>>>>>>> > _______________________________________________
>>>>>>> > Devel mailing list -- devel@ovirt.org
>>>>>>> > To unsubscribe send an email to devel-le...@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/7RTHHBALWRSJAJNTLLSLVDHB6DBKWBIK/
>>>>>>>
>>>>>>> --
>>>>>>> Anton Marchukov
>>>>>>> Team Lead - Release Management - RHV DevOps - Red Hat
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> SANDRO BONAZZOLA
>>>>>>
>>>>>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>>>>>
>>>>>> Red Hat EMEA <https://www.redhat.com/>
>>>>>>
>>>>>> sbona...@redhat.com
>>>>>> <https://red.ht/sig>
>>>>>>
>>>>> _______________________________________________
>>>>> Devel mailing list -- devel@ovirt.org
>>>>> To unsubscribe send an email to devel-le...@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/GZ7ZNVNPOH3ZXTV67MCX635PZSKCEWNZ/
>>>>>
>>>> _______________________________________________
>>>> Devel mailing list -- devel@ovirt.org
>>>> To unsubscribe send an email to devel-le...@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/J3QWUYU4TUN56RPUOGYXIP77MNGC3LSI/
>>>>
>>> _______________________________________________
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@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/YQUJCUP3PWC7YAOH45SPS7LPRRXTWKIC/
>>>
>>
>>
>> --
>> Anton Marchukov
>> Team Lead - Release Management - RHV DevOps - Red Hat
>>
>> _______________________________________________
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@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/INV4VMSF3QNYSAGDV25CCWLWDBJBES7X/
>>
>
>
> --
> Didi
>


-- 

GALIT ROSENTHAL

SOFTWARE ENGINEER

Red Hat

<https://www.redhat.com/>

ga...@gmail.com    T: 972-9-7692230
<https://red.ht/sig>
_______________________________________________
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@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/DMFRKPUSO3XGFYQGFVAXMV5XQ5OC7ES6/

Reply via email to