Bug 115811

Summary: Resin startup doesn't sort version numbers correctly
Product: [Retired] Red Hat Web Application Framework Reporter: Daniel BerrangĂ© <berrange>
Component: installationAssignee: Dennis Gregorovic <dgregor>
Status: CLOSED RAWHIDE QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-03-17 16:55:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Berrangé 2004-02-16 11:31:08 UTC 
Description of problem:
[root@camden root]# ls /opt/resin 
2.1.10  2.1.20  2.1.300  2.1.4  2.1.40
[root@camden root]# /bin/ls -d /opt/resin/* | sort -r | head -1
/opt/resin/2.1.40
[root@camden root]# 

It should have picked '2.1.300'.

It needs to be doing a numeric sort on the 3rd field, and only look
for files named 2.1.x 

Something like the following adapted code should work:

/bin/ls -d /opt/resin/2.1.* | sort -t . -k 3 -n -r | head -1

This is also relevant for tomcat.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Dennis Gregorovic 2004-02-23 21:33:27 UTC 
@40729
Comment 2 Dennis Gregorovic 2005-03-17 16:55:04 UTC 
closing old tickets