cf92d7d64d
This is a quick fix for service in rare situation that a service change state in below sequence: enabled-active --> enabled-active-failed --> disabled-failed --> enabled-active-failed When service state change directly from disabled-failed to enabled-active-failed, the failed state will not recover. Also in a seperate situation, a service failed state is cleared prematurely when the service enters into enabled-active state from enabling state because of failed/timeout audit. Since service could get into failed state because of an audit mismatch, service should be recovered to normal from failed state after a successful audit. The fix ensure service failed state is cleared after successful audit in enabled-active state. No changes in other service states. Change-Id: Ie4052fec9b1579e6da97e9e1486d7f38eafa74ea Closes-Bug: 1829880 Signed-off-by: Bin Qian <bin.qian@windriver.com> |
||
---|---|---|
api-ref/source | ||
devstack | ||
doc | ||
releasenotes | ||
service-mgmt | ||
service-mgmt-api | ||
service-mgmt-client | ||
service-mgmt-tools | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
pylint.rc | ||
test-requirements.txt | ||
tox.ini |
README.rst
ha
StarlingX Service Management