Change daily clock log to informational severity
The event log was using a severity of Error, and because the PEL message
registry had a severity of Informational, phosphor-log-manager would
spit out a trace about how the severities mismatched every time the PEL
was created.
Change-Id: Ia7559a5c3cfdf6ad93277783bfd85cb639af25a0
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
diff --git a/extensions/phal/create_pel.cpp b/extensions/phal/create_pel.cpp
index 6cbf305..c834419 100644
--- a/extensions/phal/create_pel.cpp
+++ b/extensions/phal/create_pel.cpp
@@ -239,7 +239,8 @@
return plid;
}
-void createPEL(const std::string& event, const FFDCData& ffdcData)
+void createPEL(const std::string& event, const FFDCData& ffdcData,
+ const Severity severity)
{
std::map<std::string, std::string> additionalData;
auto bus = sdbusplus::bus::new_default();
@@ -258,8 +259,7 @@
loggingInterface, "Create");
auto level =
sdbusplus::xyz::openbmc_project::Logging::server::convertForMessage(
- sdbusplus::xyz::openbmc_project::Logging::server::Entry::Level::
- Error);
+ severity);
method.append(event, level, additionalData);
auto resp = bus.call(method);
}