Actions
Bug #55578
closedmgr/dashboard: Creating and editing Prometheus AlertManager silences is buggy
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Monitoring
Target version:
% Done:
0%
Source:
Development
Tags:
Backport:
pacific, quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When creating a new monitoring silence the form is pre-filled with the wrong alert data. It is always used the alert data from the very first object in the list of the API response but not the specified alert identified by the 'fingerprint' property.
The same problem applies to editing silences. The selected silence is not edited, it's always the first one in the list returned API response but not that with the specified 'id' property.
Actions