Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

move setup/upgrade jobs to new suite in ovirt-system-tests

Description

We see more and more failures due to unavailable repos like epel.
We need some verification before running the tests and retry or abort if repos are down.

this is regadless of whether we'll mirror the repos to a more stable repo like inside oVirt.

http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/364/console

(26/2/17) Update matrix (old vs new)
red: Not included in the new suites
green: Included in the new suites

from version -> to version
3.6 -> 3.6 : We've decided that engine version 3.6 is deprecated, and shouldn't be included

3.6 -> 4.0 : We've decided that engine version 3.6 is deprecated, and shouldn't be included
4.0 -> 4.0

3.6 -> 4.1 : We've decided that engine version 3.6 is deprecated, and shouldn't be included
4.0 -> 4.1
4.1 -> 4.1

3.6 -> master : We've decided that engine version 3.6 is deprecated, and shouldn't be included
4.0 -> master
4.1 -> master
master -> master : Master already includes the latest packages. Maybe we should test master_tested -> master_latestQuestion Mark

Activity

Show:

Former user February 26, 2017 at 2:51 PM

Added old vs new comparison.

Eyal Edri February 21, 2017 at 9:12 AM

The only issue we need to check is if adding the upgrade suite adds significant amount of time to run suites, mostly because of missing baremetals for the new suite.
linking the relevant ticket here.

Former user December 13, 2016 at 5:56 PM

+ upgrade from master to exp. is fully functional (not pushed to gerrit yet, but tested locally). Hopefully I'll fix the issue with yum repo(3.6) tomorrow and start working on generating jenkins jobs.

Former user December 13, 2016 at 4:00 PM

https://gerrit.ovirt.org/#/c/67827/
Added a working suite to upgrade from 4.0 to experimental (on el7)
Now working on running the suite to upgrade from 3.6 and master. Due to centos7.3 update yesterday, I have some dependencies issues which I'm working to resolve.

The next step will be to create a jjb yaml configuration, and add this suits to the experimental flow.

Eyal Edri July 12, 2016 at 10:30 AM

With little effort we can move the setup and upgrade jobs to run as a separate suite with minimal requirements (only engine is needed) on lago and eliminate the need to move it to standard ci as independent job.

Fixed

Details

Assignee

Reporter

Blocked By

Priority

Parent

Created May 24, 2016 at 11:52 AM
Updated February 28, 2017 at 2:33 PM
Resolved February 22, 2017 at 11:20 AM

Flag notifications