In the end, forcing a restart of cephadm at least cleared the "error"
status, and nodes were not wrongly shown as offline (another symptom of the
cephadm state).
One pending OSD creation did proceed.
It still keeps trying to apply the rule and logs it as a warning now rather
than crashing.
On Wed
it looks like you've hit https://tracker.ceph.com/issues/58946 which has a
candidate fix open, but nothing merged. The description on the PR with the
candidate fix says "When osdspec_affinity is not set, the drive selection
code will fail. This can happen when a device has multiple LVs where some
o
