Bug 950677

Summary: vdsm: vdsm is printing wrong version vdsm during startup
Product: Red Hat Enterprise Virtualization Manager Reporter: Dafna Ron <dron>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED DUPLICATE QA Contact: Dafna Ron <dron>
Severity: high Docs Contact:
Priority: high    
Version: 3.2.0CC: bazulay, gickowic, hateya, iheim, lpeer, pzhukov, ybronhei, ykaul
Target Milestone: ---Keywords: Regression
Target Release: 3.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-17 14:14:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 902971    
Attachments:
Description Flags
vdsm log none

Description Dafna Ron 2013-04-10 15:53:31 UTC
Created attachment 733775 [details]
vdsm log

Description of problem:

I am working with vdsm-4.10.2-14.0.el6ev.x86_64 but vdsm restart is printing version: vdsm 4.10.2.0.19.gitf9eda0a

Version-Release number of selected component (if applicable):

vdsm-4.10.2-14.0.el6ev.x86_64
sf13

How reproducible:

100%

Steps to Reproduce:
1. install vdsm-4.10.2-14.0.el6ev.x86_64 
2. restart vdsm 
3.
  
Actual results:

vdsm is printing wrong version during startup

Expected results:

vdsm should print correct version

Additional info: log


[root@cougar01 tmp]# rpm -qa |grep vdsm 
vdsm-4.10.2-14.0.el6ev.x86_64
vdsm-python-4.10.2-14.0.el6ev.x86_64
vdsm-cli-4.10.2-14.0.el6ev.noarch
vdsm-xmlrpc-4.10.2-14.0.el6ev.noarch
[root@cougar01 tmp]#

Comment 2 Itamar Heim 2013-04-15 10:47:42 UTC
*** Bug 951917 has been marked as a duplicate of this bug. ***

Comment 3 Itamar Heim 2013-04-15 10:48:50 UTC
*** Bug 951446 has been marked as a duplicate of this bug. ***

Comment 4 Douglas Schilling Landgraf 2013-04-17 14:14:23 UTC

*** This bug has been marked as a duplicate of bug 893193 ***