<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 9:34 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 5 September 2017 at 17:59, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com">stirabos@redhat.com</a>> wrote:<br>
><br>
><br>
> On Tue, Sep 5, 2017 at 2:00 PM, Dan Kenigsberg <<a href="mailto:danken@redhat.com">danken@redhat.com</a>> wrote:<br>
>><br>
>> I believe that this issue is being tackled by<br>
>> <a href="https://gerrit.ovirt.org/#/c/81444/" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/<wbr>81444/</a><br>
><br>
><br>
> No, the issue is on DWH setup side but we merged the related patches there<br>
> almost together.<br>
> Not sure why OST is consuming an older DWH rpm.<br>
<br>
</span>OST only uses packages that passed OST before + packages you explicitly add.<br>
The newer DWH setup package probably did not pass OST yet from one<br>
reason or another.<br></blockquote><div><br></div><div>OK, in order to start consuming postgres 9.5 from SCL I had to introduce a patch on ovirt-engine project and another on dwh project and I don't think that we can successfully run the test suite with just one of the two.</div><div><br></div><div>Should we simply wait or we have to manually run OST with a list of packages from the two projects in order to have it flagging them as OK?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Barak Korren<br>
RHV DevOps team , RHCE, RHCi<br>
Red Hat EMEA<br>
<a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a> | TRIED. TESTED. TRUSTED. | <a href="http://redhat.com/trusted" rel="noreferrer" target="_blank">redhat.com/trusted</a><br>
</font></span></blockquote></div><br></div></div>