[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y

[Yaniv Kaul (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907#comment-13907 ] 

Yaniv Kaul commented on OVIRT-95:
---------------------------------

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).

> [jenkins] add job to run upgrade vdsm from version X to version Y
> -----------------------------------------------------------------
>
>                 Key: OVIRT-95
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95
>             Project: oVirt - virtualization made easy
>          Issue Type: Task
>          Components: Jenkins
>    Affects Versions: Test
>            Reporter: eyal edri [Administrator]
>            Assignee: infra
>              Labels: infra,vdsm,jenkins
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.2.0-OD-03-014#72000)