Skip to content

Commit

Permalink
purge-dashboard: check for legacy group name 'grafana-server'
Browse files Browse the repository at this point in the history
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
  • Loading branch information
guits authored and mergify[bot] committed Jul 29, 2022
1 parent 7425edd commit e74f36e
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions infrastructure-playbooks/purge-dashboard.yml
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,17 @@
invoking the playbook"
when: ireallymeanit != 'yes'

- name: import_role ceph-defaults
import_role:
name: ceph-defaults

- name: check if a legacy grafana-server group exists
import_role:
name: ceph-facts
tasks_from: convert_grafana_server_group_name.yml
when: groups.get((grafana_server_group_name | default('grafana-server')), []) | length > 0


- name: gather facts on all hosts
hosts:
- "{{ mon_group_name|default('mons') }}"
Expand Down

0 comments on commit e74f36e

Please sign in to comment.