So I was able to reproduce it. I created a Octopus cluster, created a
couple of OSDs, the device_health_metrics pool was automatically
created as expected:
2024-09-29T20:14:21.225+ 7ff3b6c8e700 0 mon.soc9-ceph@0(leader)
e1 handle_command mon_command({"prefix": "osd pool rename", "forma
Thanks for chiming in, Patrick.
Altough I can't rule it out, I doubt that anyone except me was on the
cluster after we performed the upgrade. It had a very low priority for
the customer. Do you think that if I deleted the device_health_metrics
pool and started a legacy mgr, it would recreat
On Tue, Aug 27, 2024 at 6:49 AM Eugen Block wrote:
>
> Hi,
>
> I just looked into one customer cluster that we upgraded some time ago
> from Octopus to Quincy (17.2.6) and I'm wondering why there are still
> both pools, "device_health_metrics" and ".mgr".
>
> According to the docs [0], it's suppos
