summaryrefslogtreecommitdiff
path: root/src/store/modules
diff options
context:
space:
mode:
authorLei YU <yulei.sh@bytedance.com>2021-06-22 10:30:00 +0300
committerDerick Montague <derick.montague@ibm.com>2021-07-21 21:05:17 +0300
commitcad5bb9cfc7cc4ce2024b7b227affb3c7a717f1f (patch)
tree02c8d1dc64524d53ed9626c4faab429cbdbd6fac /src/store/modules
parent06d53863a83c003e7248f5cfc8362765882d19bb (diff)
downloadwebui-vue-cad5bb9cfc7cc4ce2024b7b227affb3c7a717f1f.tar.xz
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
Diffstat (limited to 'src/store/modules')
0 files changed, 0 insertions, 0 deletions