PEL: Use uppercase hex in message registry
The code in the Registry class requires the ReasonCode field in the
message registry to use upper case hex digits (A-F) to be able to find a
match to print the description in peltool, so change the message
registry schema to require that. Also fix an entry that had lower case.
Alternatively, the code could be fixed, but with the schema checking
that runs in CI to catch errors this method seems less impactful.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: I4f26c876575be58232f1408f9357465a3340002a
diff --git a/extensions/openpower-pels/registry/schema/schema.json b/extensions/openpower-pels/registry/schema/schema.json
index 3a2ac42..11885e5 100644
--- a/extensions/openpower-pels/registry/schema/schema.json
+++ b/extensions/openpower-pels/registry/schema/schema.json
@@ -86,7 +86,7 @@
"componentID": {
"description": "The component ID of the PEL creator, in the form 0xYY00. For BD SRCs, this is optional and if not present the component ID will be taken from the upper byte of the reason code.",
"type": "string",
- "pattern": "^0x[0-9a-fA-F]{2}00$"
+ "pattern": "^0x[0-9A-F]{2}00$"
},
"src": {
@@ -151,7 +151,7 @@
"reasonCode": {
"description": "String representation of the 2 byte reason code, like 0xABCD. The reason code is the 2nd half of the 8 character SRC ASCII String field, such as B1FFABCD.",
"type": "string",
- "pattern": "^0x[0-9a-fA-F]{4}$",
+ "pattern": "^0x[0-9A-F]{4}$",
"examples": ["0x3355"]
},