Bug 1577200 - Failed to get latest vdsm version after upgrading the host to the layer rhvh-4.1-0.20180126.0+1.
Summary: Failed to get latest vdsm version after upgrading the host to the layer rhvh-...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: imgbased
Version: 4.1.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-11 13:04 UTC by Abhishekh Patil
Modified: 2019-05-16 13:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-11 13:46:35 UTC
oVirt Team: Virt
Target Upstream Version:


Attachments (Terms of Use)

Description Abhishekh Patil 2018-05-11 13:04:17 UTC
Description of problem:

After upgrading to rhvh-4.1-0.20180126.0+1, failed to get the latest version of vdsm (which is vdsm-4.19.51).

Version-Release number of selected component (if applicable):
Hypervisor version:- rhvh-4.1-0.20180126.0+1

How reproducible:
100%

Steps to Reproduce:
1.Download the old hypervisor image (I used  RHVH-4.1-20180128.0-RHVH-x86_64-dvd1.iso).
2. Install a hypervisor with the image mentioned above.
3.check the vdsm version. 
 
   it should be vdsm-4.19.45-1.el7ev.x86_64
4. update the hypervisor using 'yum update' 
5. Check the vdsm version

Actual results:

Even after upgrade to latest image vdsm version is as given below:-

  # rpm -qa vdsm
vdsm-4.19.45-1.el7ev.x86_64


Expected results:

We should be able to get latest vdsm version which is vdsm-4.19.51.

Additional info:

Comment 1 Ryan Barry 2018-05-11 13:46:35 UTC
vdsm is not shipped separately in RHVH channels.

RHVH is updated as a single system image. After a new version of redhat-virtualization-host-image-update is installed, when you reboot, you will see the version contained in the image.

Comment 2 Franta Kust 2019-05-16 13:03:52 UTC
BZ<2>Jira Resync


Note You need to log in before you can comment on or make changes to this bug.