Hm, I don't know much about ceph-ansible. Did you check if there was
any config set for a specific daemon or something, which would
override the config set? For example, 'ceph config show-with-defaults
mon.<MON>' for each mon, and then also check 'ceph config dump | grep
rule'. I would also probably grep for crush_rule in all the usual
places.
Zitat von Florian Haas <florian@xxxxxxxxxxxxxx>:
On 25/09/2024 15:21, Eugen Block wrote:
Hm, do you have any local ceph.conf on your client which has an
override for this option as well?
No.
By the way, how do you bootstrap your cluster? Is it cephadm based?
This one is bootstrapped (on Quincy) with ceph-ansible. And when the
"ceph config set" change didn't make a difference, I did also make a
point of cycling all my mons and osds (which shouldn't be necessary,
but I figured I'd try that, just in case).
And I also confirmed this same issue, in Quincy, after the cluster
was adopted into cephadm management. At that point, the behaviour
was still unchanged.
It was only after I upgraded the cluster to Reef, with
cephadm/ceph orch, that the problem went away.
Cheers,
Florian
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
