I have attached the sanitized bundle for this deployment. We have two ceph clusters, which is necessary for ceph-rbd-mirror, obviously, but they are in a single model. I don't believe this is germane to this bug so two models with cross model relations should also be sufficient.
We have multiple cinder-ceph charms deployed here but only one with pool-type=erasure-coded should be necessary.
Once the cinder-ceph charm creates its pool, rbd-mirror will try to mirror it and the above error will show up in the /var/log/ceph/ceph-client.rbd-mirror.*.log file.
Alternately, one could manually create a ceph pool with erasure coding and not need cinder-ceph at all.
I have attached the sanitized bundle for this deployment. We have two ceph clusters, which is necessary for ceph-rbd-mirror, obviously, but they are in a single model. I don't believe this is germane to this bug so two models with cross model relations should also be sufficient.
We have multiple cinder-ceph charms deployed here but only one with pool-type= erasure- coded should be necessary.
Once the cinder-ceph charm creates its pool, rbd-mirror will try to mirror it and the above error will show up in the /var/log/ ceph/ceph- client. rbd-mirror. *.log file.
Alternately, one could manually create a ceph pool with erasure coding and not need cinder-ceph at all.