Skip to:

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

[jenkins] add job to run upgrade vdsm from version X to version Y

Description

vdsm upgrade should be tested. (following on bug that was found).

suggested flow:

1. install vdsm version X (e.g from 3.2)
2. build latest vdsm version (3.3 or master)
3. yum update vdsm
4. check if service is up and running.

Activity

Show:

Eyal Edri November 28, 2016 at 9:18 AM

we'll implement this as part of #OVIRT-567,
as second step for upgrading hypervisors after engine upgrade.

Yaniv Kaul March 15, 2016 at 8:15 AM

Theoretically, of course. Practically, I'm not sure Lago is ready yet for upgrade tests (you need to add that upgrade tests to the previous version or something).
Interesting topic to tackle actually - upgrade from 3.6 to master. Let me think about it a bit (especially concerned with the new repos and how we add them intelligently).

Eyal Edri March 15, 2016 at 8:08 AM

Can we add a functional test based on Lago to vdsm to do this?
Upgrade vdsm from 3.5->3.6, 3.6->3.6,3.6->4.0.

Eyal Edri February 9, 2016 at 12:44 PM


can this kind of test be covered under functional tests, now using lago?

Eyal Edri December 3, 2015 at 10:01 AM

in this flow can covered in a vdsm functional test?

Duplicate

Details

Assignee

Reporter

Components

Priority

Parent

Created November 13, 2013 at 12:47 PM
Updated May 25, 2017 at 11:30 AM
Resolved November 28, 2016 at 9:18 AM