watchdog: Update host watchdog event name triggered
When the watchdog timer hits, if the hostboot-dump-collection is
disabled, the org.open_power.Host.Boot.Error.WatchdogTimedOut event is
triggered.
If the hostboot-dump-collection is enabled, the
org.open_power.Host.Boot.Error.WatchdogTimeout event is triggered
Due to this, when host dump collection is disabled, the event did not
match any entry in registry entry. Changing the event name and the
message registry in both enabled and disabled cases to
org.open_power.Host.Boot.Error.WatchdogTimedOut to see the expected PEL.
Fix: Update the event name to
org.open_power.Host.Boot.Error.WatchdogTimedOut
Test: Tested and verified that in both scenarios it creates the BD5EC101
PEL
Change-Id: Ib29e5c17dd81533370122bb2e08c30f856900496
Signed-off-by: Deepa Karthikeyan <deepakala.karthikeyan@ibm.com>
diff --git a/watchdog/watchdog_logging.cpp b/watchdog/watchdog_logging.cpp
index 1b7cd9f..49c5972 100644
--- a/watchdog/watchdog_logging.cpp
+++ b/watchdog/watchdog_logging.cpp
@@ -21,7 +21,7 @@
const uint32_t timeout)
{
- std::string eventName = "org.open_power.Host.Boot.Error.WatchdogTimeout";
+ std::string eventName = "org.open_power.Host.Boot.Error.WatchdogTimedOut";
// CreatePELWithFFDCFiles requires a vector of FFDCTuple.
auto emptyFfdc = std::vector<FFDCTuple>{};
diff --git a/watchdog_timeout.cpp b/watchdog_timeout.cpp
index 527256a..dbebc1e 100644
--- a/watchdog_timeout.cpp
+++ b/watchdog_timeout.cpp
@@ -79,7 +79,7 @@
{
log<level::ERR>(fmt::format("Exception {} occurred", e.what()).c_str());
std::string eventType =
- "org.open_power.Processor.Error.WatchdogTimeout";
+ "org.open_power.Host.Boot.Error.WatchdogTimedOut";
auto ffdc = std::vector<FFDCTuple>{};
std::map<std::string, std::string> additionalData;