action #174652
Updated by livdywan 5 months ago
## Motivation We need to prevent issues like #174610 (caused by work on #168811) in the future so let's use the full fqdn for each host in grafana/influxdb or as alternative use unique hostnames grafana/influxdb. ## Acceptance criteria * **AC1:** All salt minion IDs and/or states can be cleanly applied even if two hostnames (not FQDN) are unique the same, e.g. "baremetal-support" * **AC2:** All salt minion IDs equal the FQDN * **AC3:** All grafana monitored OSD hosts show current data * **AC3:** all salt minion ids are again the FQDN https://gitlab.suse.de/openqa/salt-states-openqa#how-to-use ## Suggestions * Follow up with https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1329 * Consider https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1329#note_702658 * Or maybe use different hostnames * Ensure that monitoring data on https://monitor.qa.suse.de/ continues (not that new dashboards are generated for every host) * Remove workaround from #168811-36 * Ensure that salt states can be cleanly applied even if two hostnames (not FQDN) are the same, e.g. "baremetal-support" * Ensure that all salt minion IDs equal the FQDN ## Rollback actions * Remove silence from https://monitor.qa.suse.de/alerting/silences?alertmanager=grafana `alertname=baremetal-support-prg2: host up alert`