tree 860f920447274819490953ebe571e657b1447c85
parent 68452cb09d5b9b87df48217750d4ad7eb387aedc
author Chalapathi Venkataramashetty <chalapathix.venkataramashetty@intel.com> 1621226577 +0000
committer Ed Tanous <ed@tanous.net> 1633016109 +0000

Add message registry entry for FirmwareResiliencyError

Add an event log in redfish when firmware update failed due to
FirmwareResiliencyError.

The existing message entries BMCFirmwareResiliencyError(for BMC update
failures) and BIOSFirmwareResiliencyError(for BIOS update failures) are 
not useful for the new platform. The new platform's CPLD report common 
error code for BMC, PCH or CPLD firmware update failures. Hence a common
message entry is required to capture the firmware update failure events.

This event is Implemented in the following review.
https://gerrit.openbmc-project.xyz/c/openbmc/pfr-manager/+/43281

Tested:
Redfish Service Validator passed for this change.

Update BMC firmware with mismatched SVN
POST: https://<BMC_IP>/redfish/v1/UpdateService/
      with <BMC_Update_Capsule> binary file
After BMC reboots check for Event log in Redfish
Command: GET: https://<BMC_IP>/redfish/v1/Systems/system/LogServices/
              EventLog/Entries
Response:
{
            "@odata.id": "/redfish/v1/Systems/system/LogServices/
             EventLog/Entries/1621435142_1",
            "@odata.type": "#LogEntry.v1_4_0.LogEntry",
            "Created": "2021-05-19T14:39:02+00:00",
            "EntryType": "Event",
            "Id": "1621435142_1",
            "Message": "Firmware resiliency error. Error reason:
             Firmware update failed(MinorCode:0x02).",
            "MessageArgs": [
                "Firmware update failed(MinorCode:0x02)"
            ],
            "MessageId": "OpenBMC.0.1.FirmwareResiliencyError",
            "Name": "System Event Log Entry",
            "Severity": "Critical"
        },

Signed-off-by: Chalapathi Venkataramashetty <chalapathix.venkataramashetty@intel.com>
Change-Id: Id13a29ecc160b8e9e1c0b926f6caf882fa746567