From d4ffe212259125855792449c1cd4dc64bfb03eb4 Mon Sep 17 00:00:00 2001 From: Guillaume Abrioux Date: Thu, 12 Mar 2020 12:14:01 +0100 Subject: [PATCH] osd: support changing default rule even when osd_crush_location isn't defined Creating crush rules even with no crush hierarchy configuration is a valid scenario so we shouldn't be bound to the first task result (which configure crush hierarchy) to be able to add new crush rules. Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1816989 Signed-off-by: Guillaume Abrioux (cherry picked from commit 5b0476385ccb00a9edb9092a183c18e2637afd5d) --- roles/ceph-osd/tasks/crush_rules.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/roles/ceph-osd/tasks/crush_rules.yml b/roles/ceph-osd/tasks/crush_rules.yml index 553d9a9565..b0d453d4a9 100644 --- a/roles/ceph-osd/tasks/crush_rules.yml +++ b/roles/ceph-osd/tasks/crush_rules.yml @@ -43,7 +43,6 @@ with_items: "{{ groups[mon_group_name] }}" run_once: true when: - - not config_crush_hierarchy.get('skipped', false) - info_ceph_default_crush_rule_yaml | default('') | length > 0 - not containerized_deployment | bool @@ -68,5 +67,4 @@ with_items: "{{ groups[mon_group_name] }}" run_once: true when: - - not config_crush_hierarchy.get('skipped', false) - info_ceph_default_crush_rule_yaml | default('') | length > 0