State Manager: POR reset reason is not logged

[gkeishin]

Expected Behavior

https://github.com/openbmc/phosphor-dbus-interfaces/blob/388b58f9a878f45b8ec243152cac5eb44ec90ced/yaml/xyz/openbmc_project/State/BMC.interface.yaml

    - name: RebootCause
      description: >
          The recorded reboot cause of the BMC
      values:
          - name: "POR"
            description: >
                Last reboot is caused by Power-On-Reset
          - name: "PinholeReset"
            description: >
                Last reboot is caused by pinhole reset
          - name: "Watchdog"
            description: >
                Last reboot is caused by Watchdog
          - name: "Unknown"
            description: >
                Last reboot is caused by Unknown

Actual Behavior

peltool -l | more
{
    "0x50000178": {
        "SRC":                  "110000AC",
        "Message":              "Input power was lost while the system was powered on.",
        "PLID":                 "0x50000178",
        "CreatorID":            "BMC",
        "Subsystem":            "Power/Cooling",
        "Commit Time":          "07/08/2022 14:28:01",
        "Sev":                  "Critical Error, Scope of Failure unknown",
        "CompID":               "0x2700"
    },

busctl get-property xyz.openbmc_project.State.BMC /xyz/openbmc_project/state/bmc0 xyz.openbmc_project.State.BMC LastRebootCause
s "xyz.openbmc_project.State.BMC.RebootCause.Unknown"

Steps to Reproduce the Problem

1. AC cycle the system
2. Check the RebootCause

Specifications

• Browser: NA
• Version: NA

[gkeishin]

@geissonator ^^^

[NodeMan97]

Fix is tested and uploaded. Awaiting CI.

[NodeMan97]

merged.