PEL: Support resolution property
Support resolution property to add callouts
Tested: Created new PEL using busctl and checked for the property to
see if the value is updated. The error log daemon was restarted and the
property is checked again to make sure the value is restored.
Verified serialization of new error log by recreating it on a old code
version to make sure logs are created w/o the new property and the
daemon did not crash.
Result:
root@rainier:~# busctl get-property xyz.openbmc_project.Logging \
/xyz/openbmc_project/logging/entry/1 xyz.openbmc_project.Logging.\
Entry Resolution
s "1. Priority: High, Procedure: BMCSP02\n2. Priority: Medium, PN: \
SVCDOCS\n"
Test with location Code:
root@p10bmc:~# busctl get-property xyz.openbmc_project.Logging \
/xyz/openbmc_project/logging/entry/3 xyz.openbmc_project.Logging.Entry \
Resolution
s "1. Location Code: U78DA.ND0.1234567-P0, Priority: Medium, PN: SVCDOCS\n2. \
Priority: Low, Procedure: BMCSP02\n"
Signed-off-by: Vijay Lobo <vijaylobo@gmail.com>
Change-Id: I44eebbf794efeb8e752fff98de7c638c927982cd
diff --git a/test/openpower-pels/pel_manager_test.cpp b/test/openpower-pels/pel_manager_test.cpp
index 0facc33..7bf350f 100644
--- a/test/openpower-pels/pel_manager_test.cpp
+++ b/test/openpower-pels/pel_manager_test.cpp
@@ -231,6 +231,14 @@
{
"ReasonCode": "0x2030"
},
+ "Callouts": [
+ {
+ "CalloutList": [
+ {"Priority": "high", "Procedure": "bmc_code"},
+ {"Priority": "medium", "SymbolicFRU": "service_docs"}
+ ]
+ }
+ ],
"Documentation":
{
"Description": "A PGOOD Fault",
@@ -294,6 +302,10 @@
EXPECT_EQ(manager.getEventId(pel),
"BD612030 00000055 00000010 00000000 00000000 00000000 00000000 "
"00000000 00000000");
+ // Check if resolution property creation is good
+ EXPECT_EQ(manager.getResolution(pel),
+ "1. Priority: High, Procedure: BMCSP02\n2. Priority: Medium, PN: "
+ "SVCDOCS\n");
// Remove it
manager.erase(33);