Adding severity when reporting an error
Severity is part of the PEL User Header section, and is used
to specify the PEL severity. This commit adds an option to pass
severity parameter while logging PEL. This will help to classify PELs
based on their severity. The commit also maintains uniformity in
the PEL Error logged.
Tested: By creating the error logs(pel) in error scenarios.
Signed-off-by: Pavithra Barithaya <pavithra.b@ibm.com>
Change-Id: Ic084d49b8ffe9aaea2c36c9fefa95a10a9c1c3ec
diff --git a/host-bmc/dbus_to_host_effecters.cpp b/host-bmc/dbus_to_host_effecters.cpp
index d5aeb58..21e893d 100644
--- a/host-bmc/dbus_to_host_effecters.cpp
+++ b/host-bmc/dbus_to_host_effecters.cpp
@@ -289,14 +289,14 @@
error("Failed to decode setStateEffecterStates response, rc {RC}",
"RC", rc);
pldm::utils::reportError(
- "xyz.openbmc_project.bmc.pldm.SetHostEffecterFailed");
+ "xyz.openbmc_project.PLDM.Error.SetHostEffecterFailed");
}
if (completionCode)
{
error("Failed to set a Host effecter, cc = {CC}", "CC",
static_cast<unsigned>(completionCode));
pldm::utils::reportError(
- "xyz.openbmc_project.bmc.pldm.SetHostEffecterFailed");
+ "xyz.openbmc_project.PLDM.Error.SetHostEffecterFailed");
}
};