![]() There is a specific scenario when vim starts where threads keep stalled and then after 600s the subsystems are marked as not sane. In this situation vim is supposed to quit, but instead it stays alive but in a failed state. This commit adds an extra step in vim monitoring ocf script to test if vim rpc port is open and responding, and if not, vim is forcefully killed. Test Plan PASS: install/bootstrap/unlock AIO-SX PASS: get vim to a not-sane state and observe it being killed and restarted in this scenario Closes-bug: 1979992 Change-Id: I55777a0858507634a362e58b9da281492809a03d Signed-off-by: Heitor Matsui <HeitorVieira.Matsui@windriver.com> |
||
---|---|---|
api-ref/source | ||
devstack | ||
doc | ||
mtce-guest | ||
nfv | ||
nova-api-proxy | ||
releasenotes | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
centos_build_layer.cfg | ||
centos_dev_docker_images.inc | ||
centos_dev_wheels.inc | ||
centos_guest_image.inc | ||
centos_guest_image_rt.inc | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_stable_docker_images.inc | ||
centos_stable_wheels.inc | ||
debian_build_layer.cfg | ||
debian_pkg_dirs | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
README.rst
nfv
StarlingX NFVI Orchestration