commit bb3365cb7ed2ee17286fb9a73134b5c9b8fcf424
author Nagarjun B <nagarjunb@ami.com> Thu May 25 14:40:57 2023 +0530
committer George Keishing <gkeishin@gmail.com> Fri Jun 02 15:21:48 2023 +0000
tree e8d44816ec6ad581da447e03b55a5bda36f0ed28
parent 663c2da54c94ff23e986dd4c1ca3bd48891b2f57

Modified Set Session Invalid Privilege tetscase

Modified code to expect 0xcc instead of 0x81 as IPMI resposne
since 0x06, 0x07, 0x0f are reserved bits so ipmi response must
be 0xcc.

Tested:
Ran  robot ipmi/test_ipmi_general.robot

Change-Id: I242960619312dcaaa9af72ff41cb61f837078f53
Signed-off-by: Nagarjun B  <nagarjunb@ami.com>

ipmi/test_ipmi_general.robot

diff --git a/ipmi/test_ipmi_general.robot b/ipmi/test_ipmi_general.robot
index 8995df9..4b44a7f 100644
--- a/ipmi/test_ipmi_general.robot
+++ b/ipmi/test_ipmi_general.robot
@@ -176,6 +176,7 @@
     [Template]  Set Invalid Session Privilege Level And Verify
 
     # invalid_privilege_level
+    0x01
     0x05
     0x06
     0x07
@@ -269,7 +270,15 @@
     # Verify requested level exceeds Channel and/or User Privilege Limit.
     ${msg}=  Run Keyword And Expect Error  *  Run External IPMI Raw Command
     ...  0x06 0x3b ${privilege_level}
-    Should Contain  ${msg}  Unknown  rsp=0x81
+
+    # 0x05 is OEM proprietary level.
+    IF  ${privilege_level} == 0x05
+        Should Contain  ${msg}  Unknown  rsp=0x81
+    ELSE
+        # According to IPMI spec privelege level except 0x00-0x05, others are reserved. So if we
+        # try to set those privelege we will get rsp as 0xcc(Invalid data filed in request)
+        Should Contain  ${msg}  Invalid data field in request  rsp=0xcc
+    END
 
 
 Verify Identify LED State Via Redfish