sm services loss of redundancy alarms on install of storage system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Bin Qian |
Bug Description
Brief Description
-----------------
On install of storage system, loss of redundancy alarms were observed for sm services.
Severity
--------
Critical
Steps to Reproduce
------------------
Install system
Expected Behavior
------------------
System should be alarm free at the end of install
Actual Behavior
----------------
The following alarms were seen:
+------
| Alarm ID | Reason Text | Entity ID | Severity | Time Stamp |
+------
| 400.002 | Service group controller-services loss of redundancy; expected 1 standby member but no standby members available | service_
| 400.002 | Service group cloud-services loss of redundancy; expected 1 standby member but no standby members available | service_
| 400.002 | Service group vim-services loss of redundancy; expected 1 standby member but no standby members available | service_
| 400.002 | Service group storage-services loss of redundancy; expected 2 active members but only 1 active member available | service_
| 400.002 | Service group storage-
| 400.002 | Service group patching-services loss of redundancy; expected 1 standby member but no standby members available | service_
| 400.002 | Service group oam-services loss of redundancy; expected 1 standby member but no standby members available | service_
| 400.002 | Service group directory-services loss of redundancy; expected 2 active members but only 1 active member available | service_
| 400.002 | Service group web-services loss of redundancy; expected 2 active members but only 1 active member available | service_
+------
Reproducibility
---------------
Tried once.
System Configuration
-------
Storage system
Branch/Pull Time/Commit
-------
master as of 2018-10-10_20-18-00
Timestamp/Logs
--------------
2018-10-
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Targeting stx.2019.03 as this is an issue in stx master only, not in the r/2018.10 release branch