Incorrect error message "The properties are not listed in alphabetical sequence in the file CIM_ProtocolService.class"

Bug ID:254
Project:Opentestman
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:fixed
Description

The error:

The properties are not listed in alphabetical sequence in the file CIM_ProtocolService.class.xml

Analysis:

in the file CIM_ProtocolService.class.xml  error is thrown at:

<StartMode></StartMode>
 <Started></Started> 

M” ASCII code is 0x4D, while “e” is 0x65;
So, the implementation is correct. The message returned by the OTM is incorrect.

Detailed error description and Analysis:
In the OTM the comparison is based on the Unicode value of each character in the strings in the Java section of the code.
But in the shell script while comparing the xml elements it compares them by converting the tags to Capital letters.
So we are getting the following error message:
“The following properties are not listed in alphabetical sequence in the file CIM_ProtocolService.class.xml created after enumeration”.
The similar defect is present in another 10 places (while testing the profiles):

1. CLP Service   --> CIM_ProtocolService
2. Base Metrics  --> CIM_MetricService
3. DHCP Client   --> CIM_IPProtocolEndpoint
4. IP Interface  --> CIM_IPAssignmentSettingData
5. IP Interface  --> CIM_IPConfigurationService
6. IP Interface  --> CIM_IPProtocolEndpoint
7. IP Interface  --> CIM_StaticIPAssignmentSettingData
8. Role Based Authorization --> CIM_RoleBasedAuthorizationService
9. Service Processor  --> CIM_TimeService
10. Simple Identity Management --> CIM_AccountManagementService
11. Software Inventory  --> CIM_SoftwareIdentity

Section of the Shell script:

if [ "$elem" \< "$last_elem" ];then
  bash ${DBGHANDLER} ${LINENO} "check_order() - Failed as the         \"$elem\" \< \"$last_elem\"" "ERROR"
   return 1
fi

Section of the Debug log:

========
DEBUG LOG
========
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = AVAILABLEREQUESTEDSTATES
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = CAPTION
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = COMMUNICATIONSTATUS
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = CREATIONCLASSNAME
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = DESCRIPTION
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = DETAILEDSTATUS
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = ELEMENTNAME
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = ENABLEDDEFAULT
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = ENABLEDSTATE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = HEALTHSTATE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = INSTALLDATE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = NAME
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = OPERATINGSTATUS
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = OPERATIONALSTATUS
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = OTHERENABLEDSTATE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = PRIMARYOWNERCONTACT
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = PRIMARYOWNERNAME
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = PRIMARYSTATUS
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = REQUESTEDSTATE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = STARTMODE
[DEBUG: ./etc/scripts/profile.sh at #153] check_order() - elem = STARTED
[ERROR: ./etc/scripts/profile.sh at #159] check_order() - Failed as the "STARTED" \< "STARTMODE"
[ERROR: ./etc/scripts/profile.sh at #2302] FAIL: The 1 properties are not in alphabetical order (violate WS-CIM Mapping spec section 7.3.1) for the instances of the CIM_RoleBasedAuthorizationService belonging to the ROLE BASED AUTHORIZATION PROFILE

Updates

#1 submitted by akash_malhotra on Wed, 09/17/2008 - 03:25
Status:active» fixed

This issue has been fixed in OTM 2976

#2 submitted by sanjibkjena on Mon, 09/22/2008 - 11:39

Thanks for the fix.
When will the OTM, with this fix, be released?