config/sysinv/sysinv/sysinv/sysinv/conductor
rummadis a3a20fcf59 Prune stale backup in progress alarm 210.001
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>
2024-03-22 14:44:47 -04:00
..
__init__.py StarlingX open source release updates 2018-05-31 07:35:52 -07:00
ceph.py Fix no-member errors in legacy sysinv ceph code 2023-03-15 13:14:32 +00:00
docker_registry.py Reduce pagination limit for registry requests 2023-07-24 18:44:30 +00:00
keystone_listener.py New RESTful API and DB schema for network to address-pools. 2024-03-06 07:34:14 -03:00
kube_app.py Merge "Fix delete process to apps that have charts disabled" 2024-03-07 13:43:22 +00:00
manager.py Prune stale backup in progress alarm 210.001 2024-03-22 14:44:47 -04:00
openstack.py Retry get openstack users when unauthorized 2023-08-28 13:12:00 -04:00
rpcapi.py Fix LDAP issue for DC subcloud 2024-03-13 14:27:13 -04:00
rpcapiproxy.py Add ZeroMQ RPC backend 2022-11-24 13:28:01 -03:00
rpcapizmq.py Add ZeroMQ RPC backend 2022-11-24 13:28:01 -03:00