PEL: Remove hardcoded sev for Hard shutdown err
The HardShutdownAlarmHigh error is posted twice when there is an ambient
temp high enough that it crosses the hard shutdown threshold and causes
a shutdown. The first time is when the threshold alert first occurs,
and the second is when the shutdown timer expires and the shutdown
commences.
It is desired that these two logs have different severities, the first a
PEL severity of Unrecoverable, and the second a severity of Critical.
To do this, the severity had to stop being hardcoded in the registy so
that the caller can just pass in the desired severity at the time of
creation.
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
Change-Id: Id294a3d799a9b657fe69789c61358b4df0345b93
diff --git a/extensions/openpower-pels/registry/message_registry.json b/extensions/openpower-pels/registry/message_registry.json
index 77beca9..9294aa5 100644
--- a/extensions/openpower-pels/registry/message_registry.json
+++ b/extensions/openpower-pels/registry/message_registry.json
@@ -1959,7 +1959,6 @@
"Name": "xyz.openbmc_project.Sensor.Threshold.Error.HardShutdownAlarmHigh",
"Subsystem": "power",
"ComponentID": "0x2800",
- "Severity": "unrecoverable",
"ActionFlags": ["service_action", "report"],
"SRC": {