Updating mgr’s to 18.2.5 seemed to work just fine. I will go for the remaining
services after the weekend. Thanks.
-jeremy
> On Thursday, Apr 10, 2025 at 6:37 AM, Eugen Block (mailto:ebl...@nde.ag)> wrote:
> Glad I could help! I'm also waiting for 18.2.5 to upgrade our own
> cluster from Pacifi
Hello,
recently I checked my server logs for error events and got some hits for
the ceph crash service, deployed with cephadm.
When restarted, crash service logs to journald:
auth: unable to find a keyring on
/etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/c
> On Apr 11, 2025, at 10:13, gagan tiwari
> wrote:
>
> Hi Anthony,
> We will be using Samsung SSD 870 QVO 8TB disks on
> all OSD servers.
I’m a newbie to ceph and I have a 4 node cluster and it doesn’t have a lot of
users so downtime is easily scheduled for tinkering
> On Apr 13, 2025, at 12:00 PM, Brendon Baumgartner wrote:
>
>
>
>> On Apr 11, 2025, at 10:13, gagan tiwari
>> wrote:
>>
>> Hi Anthony,
>>We will be using Samsung SSD 870 QVO 8TB disks on
>> all OSD servers.
>
> I’m a newbie to ceph and I have a 4 node cluster and
I’m now seeing this:
cluster:
id: 95f49c1c-b1e8-11ee-b5d0-0cc47a8f35c1
health: HEALTH_WARN
Failed to apply 1 service(s): osd.cost_capacity
I’m assuming this is due to the fact that I’ve only upgraded mgr but I wanted
to double check before proceeding with the rest of the components.
Thanks
-jer
This looks relevant.
https://github.com/rook/rook/issues/13600#issuecomment-1905860331
> On Sunday, Apr 13, 2025 at 10:08 AM, Jeremy Hansen (mailto:jer...@skidrow.la)> wrote:
> I’m now seeing this:
>
> cluster:
> id: 95f49c1c-b1e8-11ee-b5d0-0cc47a8f35c1
> health: HEALTH_WARN
> Failed to apply 1
