sw-manager patch-strategy failed to install due to timeout
As part of this fix, new parameter ignore_alarm_conditional
is added, which has the list of stale alarms that needs to
ignored after 30mins.
Alarm clear wait step checks for stale alarm 750.006 for
30mins. If the alarm is still not cleared, patch-strategy
ignores the alarm.
Now, since the stale alarms are monitored for 30mins,
the overall alarm clear timeout is increased to 2400sec.
In the current case alarm 750.006 is not getting cleared
and also it is not part of the ignore alarm list
so the patch-strategy times out.
Test Plan:
PASSED: Applying a patch - On DX system(VM),
Create and apply patch strategy,
fm alarm-list to have an uncleared alarm(for test purpose
100.103 - Memory threshold alarm was used). After 30mins
alarm was ignored and patch strategy successfully applied.
PASSED: Removing a patch - On DX system(VM),
Create and apply patch strategy,
fm alarm-list to have an uncleared alarm(for test purpose
100.103 - Memory threshold alarm was used). After 1800sec
alarm was ignored and patch strategy successfully applied.
PASSED: On DX system(lab), 4 consecutive patch orchestration
successfully applied. 750.006 - stale alarm tested.
PASSED: On DX system, create and apply strategy,
with alarm existing on system(not part of ignore list)
strategy would wait for 2400sec before timing out.
PASSED: On DX system, k8s upgrade from v1.21.8 to
v1.22.5 successfully executed.
Reviewed: https:/ /review. opendev. org/c/starlingx /nfv/+/ 914559 /opendev. org/starlingx/ nfv/commit/ eca1a05b8310cfb 2878a1921fe6523 6fae78ec5b
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit eca1a05b8310cfb 2878a1921fe6523 6fae78ec5b
Author: Vanathi.Selvaraju <email address hidden>
Date: Wed Mar 27 15:53:55 2024 -0400
sw-manager patch-strategy failed to install due to timeout
As part of this fix, new parameter ignore_ alarm_condition al
is added, which has the list of stale alarms that needs to
ignored after 30mins.
Alarm clear wait step checks for stale alarm 750.006 for
30mins. If the alarm is still not cleared, patch-strategy
ignores the alarm.
Now, since the stale alarms are monitored for 30mins,
the overall alarm clear timeout is increased to 2400sec.
In the current case alarm 750.006 is not getting cleared
and also it is not part of the ignore alarm list
so the patch-strategy times out.
Test Plan:
PASSED: Applying a patch - On DX system(VM),
Create and apply patch strategy,
fm alarm-list to have an uncleared alarm(for test purpose
100.103 - Memory threshold alarm was used). After 30mins
alarm was ignored and patch strategy successfully applied.
PASSED: Removing a patch - On DX system(VM),
Create and apply patch strategy,
fm alarm-list to have an uncleared alarm(for test purpose
100.103 - Memory threshold alarm was used). After 1800sec
alarm was ignored and patch strategy successfully applied.
PASSED: On DX system(lab), 4 consecutive patch orchestration
successfully applied. 750.006 - stale alarm tested.
PASSED: On DX system, create and apply strategy,
with alarm existing on system(not part of ignore list)
strategy would wait for 2400sec before timing out.
PASSED: On DX system, k8s upgrade from v1.21.8 to
v1.22.5 successfully executed.
Closes-Bug: 2059305 7e45f3af7e5ca58 8ce3ee06156
Change-Id: I7ebaf5a24fa45a
Signed-off-by: Vanathi.Selvaraju <email address hidden>