tree 864deac5e8ba18bea51b3b96400573eece5cbc66
parent bc0c6190c2ddf840201722b7b0b12b305c479ee4
author Shawn McCarney <shawnmm@us.ibm.com> 1613773555 -0600
committer Shawn McCarney <shawnmm@us.ibm.com> 1613773555 -0600

PEL: Add critical error for regulators config file

Add a new message registry entry for a critical error involving the
phosphor-regulators configuration file.

The regulators application requires a valid JSON config file.  When the
application starts, if a valid file cannot be found, a non-critical
error is logged.  This error is already defined in the message registry.

However, if the chassis starts powering on and a config file still
cannot be found, a critical error should be logged.  The voltage
regulators in the system will not be configured, and this could
potentially cause hardware damage.  For example, the default output
voltage of a regulator may be too high.

The existing message registry entry cannot be reused because it gets the
PEL severity from the base BMC error log severity.  The base BMC
severity "Critical" is mapped to the PEL severity "critical".  However,
in this case the PEL severity "critical_system_term" is needed instead.
Also, the PowerFault property should be true for the critical entry and
false for the non-critical entry.

Tested:
* Ran the validation tool.
* Loaded the message registry file into a BMC simulation session.
* Verified that when the error occurred, the expected PEL was created.

Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>
Change-Id: I4950e912481dd71be40a1a176591b235e9d4c668