Bug 951446

Summary: Incorrect vdsm version if the vdsm.log.
Product: Red Hat Enterprise Virtualization Manager Reporter: Pavel Zhukov <pzhukov>
Component: vdsmAssignee: Barak <bazulay>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: urgent    
Version: 3.1.3CC: abaron, bazulay, hateya, iheim, lpeer, lyarwood, nobody, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-15 10:48:50 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    

Description Pavel Zhukov 2013-04-12 09:25:08 UTC
Description:
There is vdsm-4.10-1.9 instead of 4.10.2-1.9 in the vdsm.log

Version-Release number of selected component (if applicable):
vdsm-4.10.2-1.9.el6ev.x86_64

How reproducible:
100%
  
Actual results:
MainThread::INFO::2013-04-12 04:31:52,093::vdsm::88::vds::(run) I am the actual vdsm 4.10-1.9 rhevh-4.gsslab.rdu2.redhat.com (2.6.32-358.2.1.el6.x86_64)


Expected results:
MainThread::INFO::2013-04-12 04:31:52,093::vdsm::88::vds::(run) I am the actual vdsm 4.10.2-1.9 rhevh-4.gsslab.rdu2.redhat.com (2.6.32-358.2.1.el6.x86_64)


Additional info:
# Setting software_version and software_revision in dsaversion.py
baserelease=`echo "%{release}" | sed 's/\([0-9]\+\(\.[0-9]\+\)\?\).*/\1/'`
baseversion=`echo "%{version}" | sed 's/\([0-9]\+\(\.[0-9]\+\)\?\).*/\1/'`
sed -i -e 's/^software_version =.*/software_version = "'"${baseversion}"'"/' \
       -e 's/^software_revision =.*/software_revision = "'"${baserelease}"'"/' vdsm/dsaversion.py

should be 
baseversion=`echo "%{version}"  | sed 's/\([0-9]\+\(\.[0-9]\+\)\?\)+.*/\1/'   ??

Comment 2 Itamar Heim 2013-04-15 10:48:50 UTC

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