PEL: Add a test error to the message registry
This error has both procedure and symbolic FRU callouts. Defining these
callouts in the registry is the only way to have these types of
callouts added to a PEL.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Ie64c11b0dac946542f43c495c20090419d71a4d7
diff --git a/extensions/openpower-pels/registry/message_registry.json b/extensions/openpower-pels/registry/message_registry.json
index 55ef4f8..b4bf308 100644
--- a/extensions/openpower-pels/registry/message_registry.json
+++ b/extensions/openpower-pels/registry/message_registry.json
@@ -315,6 +315,35 @@
},
{
+ "Name": "org.open_power.Logging.Error.TestError1",
+ "Subsystem": "platform_firmware",
+ "Severity": "unrecoverable",
+
+ "SRC":
+ {
+ "ReasonCode": "0x2003",
+ "Words6To9":
+ {
+ }
+ },
+
+ "Callouts": [
+ {
+ "CalloutList": [
+ {"Priority": "high", "Procedure": "bmc_code"},
+ {"Priority": "medium", "SymbolicFRU": "service_docs"}
+ ]
+ }
+ ],
+
+ "Documentation":
+ {
+ "Description": "An error for testing",
+ "Message": "This is a test error"
+ }
+ },
+
+ {
"Name": "org.open_power.PHAL.Error.Boot",
"Subsystem": "cec_hardware",
"Severity": "unrecoverable",