mirror of https://github.com/ceph/ceph-ansible.git
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 <gabrioux@redhat.com>pull/5227/head
parent
9219991441
commit
5b0476385c
|
@ -43,7 +43,6 @@
|
||||||
with_items: "{{ groups[mon_group_name] }}"
|
with_items: "{{ groups[mon_group_name] }}"
|
||||||
run_once: true
|
run_once: true
|
||||||
when:
|
when:
|
||||||
- not config_crush_hierarchy.get('skipped', false)
|
|
||||||
- info_ceph_default_crush_rule_yaml | default('') | length > 0
|
- info_ceph_default_crush_rule_yaml | default('') | length > 0
|
||||||
|
|
||||||
- name: "add new default crush rule to {{ cluster }}.conf"
|
- name: "add new default crush rule to {{ cluster }}.conf"
|
||||||
|
@ -56,5 +55,4 @@
|
||||||
with_items: "{{ groups[mon_group_name] }}"
|
with_items: "{{ groups[mon_group_name] }}"
|
||||||
run_once: true
|
run_once: true
|
||||||
when:
|
when:
|
||||||
- not config_crush_hierarchy.get('skipped', false)
|
|
||||||
- info_ceph_default_crush_rule_yaml | default('') | length > 0
|
- info_ceph_default_crush_rule_yaml | default('') | length > 0
|
||||||
|
|
Loading…
Reference in New Issue