summaryrefslogtreecommitdiffstats
path: root/bmc_state_manager.hpp
diff options
context:
space:
mode:
authorWilliam A. Kennington III <wak@google.com>2018-06-28 16:18:37 -0700
committerWilliam A. Kennington III <wak@google.com>2018-06-28 17:40:05 -0700
commit9a2f37cf223312f7a69bf924eb1ad63c93424109 (patch)
tree2bc92aca965482e23c3173987477535c5fbc6fe4 /bmc_state_manager.hpp
parent09568ff7d87186080b5cd3032e7ad4658c676eee (diff)
downloadphosphor-state-manager-9a2f37cf223312f7a69bf924eb1ad63c93424109.tar.gz
phosphor-state-manager-9a2f37cf223312f7a69bf924eb1ad63c93424109.zip
chassis-state-manager: Check for dbus call errors
Making the query to the power state manager can fail if that daemon does not come up before the chassis state manager. Since we added exceptions to sdbusplus for call errors, we get an unhandled exception if this daemon is not running. Since the pgood daemon will announce the power status when it starts up, we can just assume the power is off if the call fails. Eventually it will become correct. This restores the same behavior we had in the past. Tested: Ran on a zaius machine and it no longer fails / prints errors in the common cases and eventually gets to the proper state. Change-Id: I78809d747219f1096e0ea36905199a35e3b93caa Signed-off-by: William A. Kennington III <wak@google.com>
Diffstat (limited to 'bmc_state_manager.hpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud