500fbaa133
Restarting sysinv while an application is applying will result in a wrong reset status. For example cert-manager status is reset to 'apply-failed' instead of 'uploaded'. When sysinv is restarted, app operations that are in progress are reset. When apps were decoupled from sysinv [1], a requirement to have the app metadata loaded was introduced. Tests on AIO-SX: PASS: deploy, unlocked enabled available PASS: forced 'cert-manager' to be 'applying', forced sysinv conductor restart, observed status was reset to 'uploaded'. [1]: https://review.opendev.org/c/starlingx/config/+/774292/10/sysinv/sysinv/sysinv/sysinv/conductor/kube_app.py#333 Partial-Bug: 2003198 Signed-off-by: Dan Voiculeasa <dan.voiculeasa@windriver.com> Change-Id: Ibefc6362c7a7f03571be3cf35b6592cf0c68bca3 |
||
---|---|---|
api-ref/source | ||
config-gate | ||
controllerconfig | ||
devstack | ||
doc | ||
releasenotes | ||
storageconfig | ||
sysinv | ||
tmp/patch-scripts/EXAMPLE_SYSINV/scripts | ||
tools/docker/images | ||
tsconfig | ||
workerconfig | ||
.gitignore | ||
.gitreview | ||
.yamllint | ||
.zuul.yaml | ||
CONTRIBUTORS.wrs | ||
LICENSE | ||
README.rst | ||
bindep.txt | ||
centos_build_layer.cfg | ||
centos_dev_wheels.inc | ||
centos_iso_image.inc | ||
centos_pkg_dirs | ||
centos_pkg_dirs_containers | ||
centos_stable_wheels.inc | ||
debian_build_layer.cfg | ||
debian_iso_image.inc | ||
debian_pkg_dirs | ||
debian_stable_wheels.inc | ||
test-requirements.txt | ||
tox.ini |
README.rst
stx-config
StarlingX Configuration Management