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 |
||
---|---|---|
.. | ||
.eggs | ||
contrib | ||
doc/source | ||
etc/sysinv | ||
scripts | ||
sysinv | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.stestr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
openstack-common.conf | ||
pylint.rc | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
upper-constraints.txt |
README.rst
Placeholder to allow setup.py to work. Removing this requires modifying the setup.py manifest.