Alarm audit is happening too frequently during VIM orchestration

Bug #1921127 reported by Bart Wensley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Low
Al Bailey

Bug Description

Brief Description
-----------------
When the VIM does runs orchestration, it periodically queries alarms to keep track of the health of the system. The intent was that this should be done every 30 seconds, but the code is currently doing this query approximately every 4 seconds for Firmware, Upgrade and Kubernetes Upgrade orchestration. The query is being done at the correct interval for Patch orchestration.

There is no real functional impact - just unnecessary messaging from the VIM to the Fault Management component and extra logs in nfv-vim.log.

Severity
--------
Minor

Steps to Reproduce
------------------
Run one of the above mentioned orchestrations with the VIM.

Expected Behavior
------------------
Alarms should be audited roughly every 30 seconds.

Actual Behavior
----------------
Alarms are audited every 4 seconds.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
All

Branch/Pull Time/Commit
-----------------------
All (day one issue)

Last Pass
---------
Never

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Developer Testing

Workaround
----------
None

Tags: stx.nfv
Ghada Khalil (gkhalil)
Changed in starlingx:
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nfv (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/nfv/+/796096

Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nfv (master)

Reviewed: https://review.opendev.org/c/starlingx/nfv/+/796096
Committed: https://opendev.org/starlingx/nfv/commit/a7b23615e38467f977532b53de2317e6d3cbaccb
Submitter: "Zuul (22348)"
Branch: master

commit a7b23615e38467f977532b53de2317e6d3cbaccb
Author: albailey <email address hidden>
Date: Wed Mar 24 15:09:33 2021 -0500

    Reset alarm timers back to 30 after orch sets them to 2

    The alarm audit is set to 2 seconds by an alarm callback.
    Once that callback has been processed, need to reset the
    timer back to its default of 30 seconds.

    Note: Patch orch did not encounter this issue, because its
    audit called other code after the alarm callback, which reset
    the timer.

    Closes-Bug: 1921127
    Change-Id: Iba82c71757c0a9e760926e81a42ba91b14196e0e
    Signed-off-by: albailey <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.