a3a20fcf59
User unable to take subcloud backup when there is a stale backup in progress alarm Example: When user tries to take subcloud backup in Distributed cloud env if there is stale 210.001 alarm present in subcloud then user can not trigger the subsequent subcloud backup This Fix helps to identify the 210.001 alarms and clear them if they are pending more than 1 hour TEST PLAN: PASS: DC-libvirt setup with 2 controllers and 2 subclouds PASS: verified stale 210.001 getting removed Closes-Bug: 2058516 Change-Id: Iedcc5e41cd4245c538d331d9aa8c2b6cc445acce Signed-off-by: rummadis <ramu.ummadishetty@windriver.com> |
||
---|---|---|
.. | ||
.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.