Re: [ovirt-devel] [ OST Failure Report ] [ ovirt-engine-4.1 ] [ 02.03.2017 ] [004_basic_sanity]
+ infra On Thu, Mar 16, 2017 at 5:32 PM, Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
On 16 March 2017 at 18:33, Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
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. 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 bkorren@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/
On Fri, Mar 17, 2017 at 8:24 AM, Barak Korren <bkorren@redhat.com> wrote:
The change was merged 2 weeks ago. How can we make sure not to waste people time next time to analyze the issue?
בתאריך 17 במרץ 2017 02:32 PM, "Piotr Kliczewski" < piotr.kliczewski@gmail.com> כתב: The change was merged 2 weeks ago. How can we make sure not to waste people time next time to analyze the issue? "Merged" is hardly "released". As long as a fix does not make it to a release, users can still come across the issue, and so can OST. I can't think of a quick way to avoid that, but I'm open to suggestions.... WRT getting more frequent oVirt releases, I'm hardly in a position to give input about that.
On Sun, Mar 19, 2017 at 10:30 AM, Oved Ourfali <oourfali@redhat.com> wrote:
As Piotr mentioned, the job is using 1.3.8 however 1.3.9 was released.....
Thanks, We will look into the logs and find out what caused it to use 1.3.8 and report here on the results, can't be sure yet if its a bug in the job or anything else.
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
On Sun, Mar 19, 2017 at 10:33 AM, Eyal Edri <eedri@redhat.com> wrote:
Let me explain what happened: 1. check-patch jobs used to run on latest 'tested' repo, but that repo is very big as it contains history of all the builds done for a release [1] 2. recently we found a bug that caused OST to fail due to out of memory because it tried to sync the entire tested repo into memory ( that's how OST works ), so the tested repo was removed from check-patch. 3. This means that now check-patch is only using the repos in the reposync file, which for 4.1 is latest released. 4. vdsm-jsonrpc-java 1.3.9 wasn't released in any official oVirt 4.1 release, this is why the job used 1.3.8 which is the latest released. 5. We also don't want to replace the default repos for OST on 4.1 to something other than released, because the basic suite per release should always check against official release [2] 6. As a side note - manual jobs also support running on latest tested, so this issue is solely restricted to 'check-patch' jobs. We do however believe that running check-patch on latest code is important, so we'll look into providing an alternate solution that won't break any of the above restrictions, Suggestions are welcome of course. [1] It is done so anyone that wants to check oVirt can do it w/o worrying that a pkg will be removed during testing ( something that was happening when used experimental lastest.tested repo ) [2] As opposed to experimental flows which DO check against latest code, which is why 4.1 experimental didn't fail on this issue, as it used 1.3.9
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
participants (4)
-
Barak Korren -
Eyal Edri -
Oved Ourfali -
Piotr Kliczewski