stuck memory alarm on AIO-SX
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| StarlingX |
Fix Released
|
Medium
|
Eric MacDonald | ||
Bug Description
With the Nov 5 load I installed and then ran "config_controller --kubernetes". Afterwards it came up with a critical memory alarm that didn't clear even after memory consumption was significantly reduced.
After stopping/starting collectd the alarm was cleared.
Talking with Eric, he indicated that the problem was related to the following log:
2018-11-
He also said that "collectd for some reason responded with a notification string that the code was never integrated to recognize. The "nan" value is unrecognixed by the fm_notifier.py file."
| Ghada Khalil (gkhalil) wrote | #1 |
| Changed in starlingx: | |
| importance: | Undecided → Medium |
| summary: |
- stuck memory alarm on AIOSX + stuck memory alarm on AIO-SX |
| Changed in starlingx: | |
| status: | New → Triaged |
| assignee: | nobody → Eric MacDonald (rocksolidmtce) |
| tags: | added: stx.2019.03 stx.metal |
| tags: |
added: stx.2019.05 removed: stx.2019.03 |
| Changed in starlingx: | |
| assignee: | Eric MacDonald (rocksolidmtce) → Cindy Xie (xxie1) |
| Changed in starlingx: | |
| assignee: | Cindy Xie (xxie1) → chen haochuan (martin1982) |
| tags: |
added: stx.2.0 removed: stx.2019.05 |
| chen haochuan (martin1982) wrote | #3 |
| Ghada Khalil (gkhalil) wrote | #4 |
| Changed in starlingx: | |
| assignee: | chen haochuan (martin1982) → Eric MacDonald (rocksolidmtce) |
| Changed in starlingx: | |
| status: | Triaged → Fix Released |
| Ghada Khalil (gkhalil) wrote | #5 |
Targeting stx.2019.03 - stuck alarm; not urgent, but should be investigated and fixed before the release date.