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/' ??
*** This bug has been marked as a duplicate of bug 950677 ***