On Fri, Mar 17, 2017 at 8:24 AM, Barak Korren <bkor...@redhat.com> wrote: > On 16 March 2017 at 18:33, Piotr Kliczewski <piotr.kliczew...@gmail.com> > wrote: >> + infra >> >> On Thu, Mar 16, 2017 at 5:32 PM, Piotr Kliczewski >> <piotr.kliczew...@gmail.com> wrote: >>> I checked the logs and I checked that the job somehow used older >>> version without the fix: >>> >>> 2017-03-16 14:16:07,212::INFO::repoman.common.stores.RPM::Adding >>> package >>> /var/lib/lago/reposync/ovirt-4.1-el7/noarch/vdsm-jsonrpc-java-1.3.8-1.el7.centos.noarch.rpm >>> to repo /dev/shm/ost/deployment-basic-suite-4.1/default/internal_repo >>> >>> How is it possible? > > The "experimental" OST flow runs against the experimental repo that > includes the latest built packages from all projects. > A vanilla clone of OST, as well as the OST check-patch job, run > against the official released repos. I guess the fixed version did not > make it to a release yet.
The change was merged 2 weeks ago. How can we make sure not to waste people time next time to analyze the issue? > > By the way, when reading the repoman log, the important lines are the > ones that start with "Saving". The lines with "Adding" just show the > packages it "sees" not the ones it eventually decides to expose to the > VMs. > > -- > Barak Korren > bkor...@redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel