phosphor-dump-manager: Set fault log type

- Set the fault log type based on the crashdump complete property.

Tested:
```
root@zoro:~# busctl tree xyz.openbmc_project.Dump.Manager
`- /xyz
  `- /xyz/openbmc_project
    `- /xyz/openbmc_project/dump
      |- /xyz/openbmc_project/dump/bmc
      `- /xyz/openbmc_project/dump/faultlog
        |- /xyz/openbmc_project/dump/faultlog/1
        | `- /xyz/openbmc_project/dump/faultlog/1/entry
        |   |- /xyz/openbmc_project/dump/faultlog/1/entry/1
        `- /xyz/openbmc_project/dump/faultlog/2
          `- /xyz/openbmc_project/dump/faultlog/2/entry
            `- /xyz/openbmc_project/dump/faultlog/2/entry/1

root@zoro:~# busctl get-property xyz.openbmc_project.Dump.Manager /xyz/openbmc_project/dump/faultlog/1/entry/1 xyz.openbmc_project.Dump.Entry.FaultLog Type
s "xyz.openbmc_project.Common.FaultLogType.FaultLogTypes.CPER"

root@zoro:~# busctl get-property xyz.openbmc_project.Dump.Manager /xyz/openbmc_project/dump/faultlog/2/entry/1 xyz.openbmc_project.Dump.Entry.FaultLog Type
s "xyz.openbmc_project.Common.FaultLogType.FaultLogTypes.Crashdump"
```

Fusion-Link:
platform5: fusion2.corp.google.com/68561309-0301-30cd-b350-054d909cf884
platform11: fusion2.corp.google.com/ee060552-6ac0-3aa2-9348-5d286c1e9413
platform15: fusion2.corp.google.com/5a9ee3c3-722e-35a2-8b89-98ae605d21e6
platform17: fusion2.corp.google.com/d6963351-33cc-3b71-a5f0-0e02dda8625a

Google-Bug-Id: 475036214
Change-Id: I06a23591671cbcc0490f2ce516fd4b3e99fc0c4d
Signed-off-by: Eugene Huang <eugene.ty.huang@fii-na.corp-partner.google.com>
1 file changed
tree: cec7b2d58a7e8e0d8b63352d65c41c6e3ec0bdda
  1. classes/
  2. conf/
  3. dynamic-layers/
  4. recipes-bsp/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-google/
  10. recipes-kernel/
  11. recipes-phosphor/
  12. recipes-support/
  13. recipes-tpm1/
  14. recipes-tpm2/
  15. LICENSE
  16. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.