PEL:phosphor-power PSU Severity updates
In customer support situations, it was found to be confusing to label
the communication failure with unrecoverable_redundancy_loss. In
addition that, it was equally confusing to label a power supply missing
as just unrecoverable, when redundancy is likely actually lost.
Swap the severity values of 0x15F2 and 0x15F6.
0x15F2 - communication failure - unrecoverable.
0x15F6 - PSU missing - unrecoverable_redundancy_loss
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
Change-Id: Ie9521100f4f32a6884b76bb3c1c7e62042f27708
diff --git a/extensions/openpower-pels/registry/message_registry.json b/extensions/openpower-pels/registry/message_registry.json
index 4835853..13db7f7 100644
--- a/extensions/openpower-pels/registry/message_registry.json
+++ b/extensions/openpower-pels/registry/message_registry.json
@@ -612,7 +612,7 @@
{
"Name": "xyz.openbmc_project.Power.PowerSupply.Error.CommFault",
"Subsystem": "power_supply",
- "Severity": "unrecoverable_redundancy_loss",
+ "Severity": "unrecoverable",
"ActionFlags": ["service_action", "report", "call_home"],
"ComponentID": "0x2700",
@@ -637,7 +637,7 @@
{
"Name": "xyz.openbmc_project.Power.PowerSupply.Error.Missing",
"Subsystem": "power_supply",
- "Severity": "unrecoverable",
+ "Severity": "unrecoverable_redundancy_loss",
"ActionFlags": ["service_action", "report", "call_home"],
"ComponentID": "0x2700",