<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 2, 2017 at 11:40 AM Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Mar 2, 2017 at 11:34 AM, Yaniv Kaul <<a href="mailto:ykaul@redhat.com" class="gmail_msg" target="_blank">ykaul@redhat.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> On Thu, Mar 2, 2017 at 11:32 AM Yedidyah Bar David <<a href="mailto:didi@redhat.com" class="gmail_msg" target="_blank">didi@redhat.com</a>> wrote:<br class="gmail_msg">
>><br class="gmail_msg">
>> On Thu, Mar 2, 2017 at 11:24 AM, Pavel Zhukov <<a href="mailto:pzhukov@redhat.com" class="gmail_msg" target="_blank">pzhukov@redhat.com</a>> wrote:<br class="gmail_msg">
>> ><br class="gmail_msg">
>> ><br class="gmail_msg">
>> > On Thu, Mar 02 2017, Sandro Bonazzola wrote:<br class="gmail_msg">
>> ><br class="gmail_msg">
>> >> ovirt-engine-hosts-ansible-inventory has been dropped in favor of<br class="gmail_msg">
>> >> ovirt-engine-metrics<br class="gmail_msg">
>> >> Maybe this is the root cause.<br class="gmail_msg">
>> > Right, I see the fix was merged <a href="https://gerrit.ovirt.org/73415" rel="noreferrer" class="gmail_msg" target="_blank">https://gerrit.ovirt.org/73415</a> and the<br class="gmail_msg">
>> > job<br class="gmail_msg">
>> > is green now.<br class="gmail_msg">
>><br class="gmail_msg">
>> We merged ovirt-engine-metrics-1.0.0 and made sure it was built correctly<br class="gmail_msg">
>> by build-artifacts, prior to merging the engine patch that needs it.<br class="gmail_msg">
>><br class="gmail_msg">
>> If that's not enough, please explain how should such things - two patches<br class="gmail_msg">
>> in two different git repos that need to be merged and then tested in a<br class="gmail_msg">
>> specific order - should be handled in the future.<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> Don't think there's a very good solution to this in our current<br class="gmail_msg">
> architecture.<br class="gmail_msg">
<br class="gmail_msg">
But for sure there is _something_ we can say, no?<br class="gmail_msg">
<br class="gmail_msg">
If I wait a day, might this not be enough either?<br class="gmail_msg"></blockquote><div><br></div><div>I don't see who's going to wait - especially as we'll be moving to running CI more and more - hopefully per patch at some point.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
> I think it's quite alright for the CI to fail on this - and then to succeed<br class="gmail_msg">
> when fixed.<br class="gmail_msg">
<br class="gmail_msg">
Of course, in general. I just want to understand what's the minimum I<br class="gmail_msg">
need to do (wait some more, something else?) to save some noise...<br class="gmail_msg"></blockquote><div><br></div><div>Mainly communication - a heads up that you are about to break CI and will fix it right after makes sense to me. There are more sophisticated solutions (Zuul?) out there, but I think straightforward communication is the easiest, at this point - it doesn't happen often.</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
> Y.<br class="gmail_msg">
><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> The relevant patches, in current case, are:<br class="gmail_msg">
>><br class="gmail_msg">
>> <a href="https://gerrit.ovirt.org/73414" rel="noreferrer" class="gmail_msg" target="_blank">https://gerrit.ovirt.org/73414</a><br class="gmail_msg">
>><br class="gmail_msg">
>> Build ovirt-engine-metrics-1.0.0.<br class="gmail_msg">
>> build-artifacts finished at 09:36 (IST).<br class="gmail_msg">
>><br class="gmail_msg">
>> <a href="https://gerrit.ovirt.org/73363" rel="noreferrer" class="gmail_msg" target="_blank">https://gerrit.ovirt.org/73363</a><br class="gmail_msg">
>><br class="gmail_msg">
>> Remove ovirt-engine-hosts-ansible-inventory,<br class="gmail_msg">
>> and require ovirt-engine-metrics, which replaces it.<br class="gmail_msg">
>> Merged at 09:40, build-artifacts finished 10:00.<br class="gmail_msg">
>><br class="gmail_msg">
>> Can we expect ost to run on packages based on the order in which they<br class="gmail_msg">
>> were merged, or built? If not, is there any other assumption we can<br class="gmail_msg">
>> make re the order? Also, can we affect this order somehow?<br class="gmail_msg">
>><br class="gmail_msg">
>> Thanks,<br class="gmail_msg">
>><br class="gmail_msg">
>> > Thank you!<br class="gmail_msg">
>> >><br class="gmail_msg">
>> >> On Thu, Mar 2, 2017 at 9:23 AM, Pavel Zhukov <<a href="mailto:pzhukov@redhat.com" class="gmail_msg" target="_blank">pzhukov@redhat.com</a>><br class="gmail_msg">
>> >> wrote:<br class="gmail_msg">
>> >><br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> Hello,<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> ovirt-engine upgrade is failed on 'rpm -q' command [2] so job [1] was<br class="gmail_msg">
>> >>> marked as<br class="gmail_msg">
>> >>> failed. It's reproducible and started from build [1] onward.<br class="gmail_msg">
>> >>> I don't see any relevant patches in otopi/engine merged recently so no<br class="gmail_msg">
>> >>> suspected patches<br class="gmail_msg">
>> >>> sp far.<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> [1] <a href="http://jenkins.ovirt.org/view/experimental%20jobs/job/test-" rel="noreferrer" class="gmail_msg" target="_blank">http://jenkins.ovirt.org/view/experimental%20jobs/job/test-</a><br class="gmail_msg">
>> >>> repo_ovirt_experimental_master/5626/<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> [2]<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 DEBUG otopi.plugins.ovirt_engine_<br class="gmail_msg">
>> >>> setup.ovirt_engine_common.distro-rpm.packages plugin.execute:926<br class="gmail_msg">
>> >>> execute-output: ('/bin/rpm', '-q', 'ovirt-engine-webadmin-portal',<br class="gmail_msg">
>> >>> 'ovirt-engine-dwh', 'ovirt-engine', 'ovirt-engine-restapi',<br class="gmail_msg">
>> >>> 'ovirt-engine-dbscripts', 'ovirt-engine-tools-backup',<br class="gmail_msg">
>> >>> 'ovirt-engine-dashboard', 'ovirt-engine-userportal',<br class="gmail_msg">
>> >>> 'ovirt-engine-wildfly', 'ovirt-engine-backend',<br class="gmail_msg">
>> >>> 'ovirt-engine-wildfly-overlay',<br class="gmail_msg">
>> >>> 'ovirt-engine-hosts-ansible-inventory',<br class="gmail_msg">
>> >>> 'ovirt-engine-tools', 'ovirt-engine-extension-aaa-jdbc') stderr:<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 DEBUG otopi.transaction transaction.abort:119<br class="gmail_msg">
>> >>> aborting<br class="gmail_msg">
>> >>> 'Yum Transaction'<br class="gmail_msg">
>> >>> Loaded plugins: fastestmirror, versionlock<br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 DEBUG otopi.transaction transaction.abort:119<br class="gmail_msg">
>> >>> aborting<br class="gmail_msg">
>> >>> 'DWH Engine database Transaction'<br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 DEBUG otopi.transaction transaction.abort:119<br class="gmail_msg">
>> >>> aborting<br class="gmail_msg">
>> >>> 'Database Transaction'<br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 DEBUG otopi.context context._executeMethod:142<br class="gmail_msg">
>> >>> method<br class="gmail_msg">
>> >>> exception<br class="gmail_msg">
>> >>> Traceback (most recent call last):<br class="gmail_msg">
>> >>> File "/usr/lib/python2.7/site-packages/otopi/context.py", line 132,<br class="gmail_msg">
>> >>> in<br class="gmail_msg">
>> >>> _executeMethod<br class="gmail_msg">
>> >>> method['method']()<br class="gmail_msg">
>> >>> File "/usr/share/otopi/plugins/otopi/core/transaction.py", line 93,<br class="gmail_msg">
>> >>> in<br class="gmail_msg">
>> >>> _main_end<br class="gmail_msg">
>> >>> self._mainTransaction.commit()<br class="gmail_msg">
>> >>> File "/usr/lib/python2.7/site-packages/otopi/transaction.py", line<br class="gmail_msg">
>> >>> 148,<br class="gmail_msg">
>> >>> in commit<br class="gmail_msg">
>> >>> element.commit()<br class="gmail_msg">
>> >>> File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-<br class="gmail_msg">
>> >>> engine-setup/ovirt-engine-common/distro-rpm/packages.py", line 146, in<br class="gmail_msg">
>> >>> commit<br class="gmail_msg">
>> >>> osetupcons.RPMDistroEnv.VERSION_LOCK_APPLY<br class="gmail_msg">
>> >>> File "/usr/lib/python2.7/site-packages/otopi/plugin.py", line 931,<br class="gmail_msg">
>> >>> in<br class="gmail_msg">
>> >>> execute<br class="gmail_msg">
>> >>> command=args[0],<br class="gmail_msg">
>> >>> RuntimeError: Command '/bin/rpm' failed to execute<br class="gmail_msg">
>> >>> 2017-03-02 02:48:13 ERROR otopi.context context._executeMethod:151<br class="gmail_msg">
>> >>> Failed<br class="gmail_msg">
>> >>> to execute stage 'Transaction commit': Command '/bin/rpm' failed to<br class="gmail_msg">
>> >>> execute<br class="gmail_msg">
>> >>><br class="gmail_msg">
>> >>> --<br class="gmail_msg">
>> >>> Pavel<br class="gmail_msg">
>> >>> _______________________________________________<br class="gmail_msg">
>> >>> Devel mailing list<br class="gmail_msg">
>> >>> <a href="mailto:Devel@ovirt.org" class="gmail_msg" target="_blank">Devel@ovirt.org</a><br class="gmail_msg">
>> >>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br class="gmail_msg">
>> >>><br class="gmail_msg">
>> ><br class="gmail_msg">
>> ><br class="gmail_msg">
>> > --<br class="gmail_msg">
>> > Pavel Zhukov<br class="gmail_msg">
>> > Software Engineer<br class="gmail_msg">
>> > RHV DevOps<br class="gmail_msg">
>> > IRC: landgraf<br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> --<br class="gmail_msg">
>> Didi<br class="gmail_msg">
>> _______________________________________________<br class="gmail_msg">
>> Devel mailing list<br class="gmail_msg">
>> <a href="mailto:Devel@ovirt.org" class="gmail_msg" target="_blank">Devel@ovirt.org</a><br class="gmail_msg">
>> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
Didi<br class="gmail_msg">
</blockquote></div></div>