Killing glance.api.pid process is not creating any kind of fm alarm-list
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Medium
|
haitao wang |
Bug Description
Brief Description
-----------------
There is any alarm once the process id of "cat /var/run/
Severity
--------
Major
Steps to Reproduce
------------------
Identify the glance-api.pid process:
Controller-# $ cat /var/run/
kill the process:
Controller-# $ sudo kill -9 ####
Verify that alarm entry is represented in GUI and includes:
alarm ID - 300.003
severity - Major
entity instance ID service_
proposed repair action Contact next level of support
reason text Service group failure; <list of affected services>. Service group degraded; <list of affected services>. Service group warning; <list of affected services>.
Make sure that "glance-api.pid " got another pid.
Controller-# $ cat /var/run/
Expected Behavior
------------------
Once the the process id of "/glance-api.pid" is killed there should be an alarm logged.
Actual Behavior
----------------
Once the process id of "glance-api.pid" is killed and a new process is assigned to it there is no alarm/event logged in the system
Reproducibility
---------------
State if the issue is 100% reproducible
System Configuration
-------
Virtual Machine - Multinode - External Storage - 2 controllers + 2 computes + 2 stororages
Branch/Pull Time/Commit
-------
NA
Timestamp/Logs
--------------
Logs attached
summary: |
- Killing glance.api.pid process is not creating any kind of fm alarm- - list. + Killing glance.api.pid process is not creating any kind of fm alarm-list |
Changed in starlingx: | |
assignee: | Cindy Xie (xxie1) → haitao wang (hwang85) |
Changed in starlingx: | |
status: | Triaged → In Progress |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
Targeting stx.2019.03 - The process recovers; it's just the alarm that's missing. This is not severe enough to block the stx.2018.10 release.