[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23320#comment-23320 ] eyal edri [Administrator] commented on OVIRT-95: ------------------------------------------------ we'll implement this as part of #OVIRT-567, as second step for upgrading hypervisors after engine upgrade.
[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 Priority: Lowest 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 (v1000.571.2#100021)