tree 02c8d1dc64524d53ed9626c4faab429cbdbd6fac
parent 06d53863a83c003e7248f5cfc8362765882d19bb
author Lei YU <yulei.sh@bytedance.com> 1624347000 +0800
committer Derick Montague <derick.montague@ibm.com> 1626890717 +0000

Fix inconsistent power status

The webui was using a websocket to subscribe the events from BMC for
server status and logging.
It uses a debouncer of 2.5 to limit the events, however, it causes the
loss of the events, so the power change status event could be missed by
the webui, causing the `Power` status is not really consistent.

There was an issue in the property change handler as well that it
assumes the `CurrentHostState` is there. However, certain event could be
fired without `CurrentHostState` change, e.g. the "ForceWarmReboot" will
get an host event of `RequestedHostTransition` without
`CurrentHostState`'s change, the code will get an undefined
`CurrentHostState` and the `Power` status becomes undetermined.

Remove the 2.5 debouncer, and only set the power status when
`CurrentHostState` is really received to fix the issue.

Tested: Verify the `Power` status is consistent with the server status.

Signed-off-by: Lei YU <yulei.sh@bytedance.com>
Change-Id: I732069fff954a2b8b1de4848115641903a8bc904