Ensure POR reset is logged
In situations where the last reboot cause is not changed to POR,
specifically after unexpected AC losses, bmc-state-manager fails to
update the property. Therefore after a power cycle the last reboot
cause property is set to unknown. Thankfully, chassis-state-manager
generates a file indicating an AC loss occurred and that can be used
to identify that the last reboot cause was a power-on-cycle. It was
necessary to add an "After xyz.openbmc_project.State.Chassis"
dependency to bmc-state-managers service file to ensure the AC loss
was generated prior to bmc-state-manager executing.
Tested:
- Ensured that when the system was power cycled that the last reboot
cause was set to "POR" when the chassis lost power file was present.
- Verified that when the file was not present the last reboot
cause was set accordingly (typically unknown)
Change-Id: Ifa6d5d6f89c221477ee2f2fa1ed15adade359e45
Signed-off-by: NodeMan97 <corey.hardesty@icloud.com>
diff --git a/service_files/xyz.openbmc_project.State.BMC.service b/service_files/xyz.openbmc_project.State.BMC.service
index 5171877..45ba6f0 100644
--- a/service_files/xyz.openbmc_project.State.BMC.service
+++ b/service_files/xyz.openbmc_project.State.BMC.service
@@ -1,6 +1,7 @@
[Unit]
Description=Phosphor BMC State Manager
Before=mapper-wait@-xyz-openbmc_project-state-bmc.service
+After=xyz.openbmc_project.State.Chassis@0.service
Wants=obmc-mapper.target
After=obmc-mapper.target
Wants=xyz.openbmc_project.Logging.service