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/discover_system_state.cpp b/discover_system_state.cpp
index 837f0d1..c94faaf 100644
--- a/discover_system_state.cpp
+++ b/discover_system_state.cpp
@@ -125,10 +125,7 @@
info("One time not set, check user setting of power policy");
#ifdef ONLY_RUN_APR_ON_POWER_LOSS
- std::string chassisLostPowerFileFmt =
- fmt::sprintf(CHASSIS_LOST_POWER_FILE, hostId);
- fs::path chassisPowerLossFile{chassisLostPowerFileFmt};
- if (!fs::exists(chassisPowerLossFile))
+ if (!phosphor::state::manager::utils::checkACLoss(hostId))
{
info(
"Chassis power was not on prior to BMC reboot so do not run any power policy");