STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app

Bug #2023657 reported by Gabriel Calixto de Paula
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
Unassigned

Bug Description

Brief Description
-------------------
After swacting to controller-1 and reapplying WRO, the 250.001 alarm does not disappear.

Severity
-------------------
Minor, 1 TC impacted during sanity

Steps to Reproduce
--------------------

Swact to controller-1 (DX Required)
reapply STX-Openstack
Expected Behavior
The 250.001 alarm should appear and disappear afterwards

Actual Behavior
-------------------
The alarm stays

Reproducibility
-------------------
Reproducible, the 1st run on our sanity causes this failure

System Configuration
--------------------
System Type: AIO-DX

Load Information
--------------------
STX + STX-Openstack master
20230611T060000Z
BUILD_DATE="2023-06-11 06:00:00 +0000"
app_version: 1.0-1.stx.49-debian-stable-versioned
build_date: 2023-06-11 19:43:45 +0000

Last Pass
----------------
May 28 STX-Openstack sanity

Alarms
-----------------------
250.001

Test Activity
-----------------------
STX-Openstack sanity

tags: added: stx.distro.openstack
Revision history for this message
Thales Elero Cervi (tcervi) wrote :

Marking as invalid based on latest Sanity execution report: https://<email address hidden>/thread/UFXM4FQSC66K5YGSYMZVHB4DE4A4JN6O/

Changed in starlingx:
status: New → Invalid
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
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.