Actions
action #161429
opencoordination #161414: [epic] Improved salt based infrastructure management
incomplete config files on OSD due to salt - create annotations in grafana on the time of the osd deployment as well as salt-states-openqa deployments
Start date:
2024-06-03
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Motivation¶
See #161324 . Why did the salt states pipelines end with success when the salt high state was never reported to be successfully applied to the openqa.suse.de salt minion (openqa.suse.de is not mentioned in the list of minions where the state was applied but the pipeline still ended)? We do not know yet but this should help us in the future to spot errors quicker in case similar problems return. Annotating grafana with times and details of potentially important changes like from osd-deployment and salt-states-openqa could help.
Acceptance criteria¶
- AC1: annotations are applied to grafana dashboards/panels on osd-deployment deployments
- AC2: Same as AC1 but for osd-deployment
Suggestions¶
- Follow https://grafana.com/docs/grafana/latest/developers/http_api/annotations/#create-annotation to create annotations from osd-deployment and salt-states-openqa deployment CI pipelines
Updated by okurz 9 months ago
- Related to action #161324: Conduct "lessons learned" with Five Why analysis for "osd not accessible, 502 Bad Gateway" added
Actions