Dear Eugen,
Thanks again for the help.
We managed to upgrade to a minor release 16.2.3, next week we will upgrade to
latest 16.2.15.
You were right about the number of manager which was blocking the update.
Thanks again for the help.
I
Topic solved.
Best Regards.
-Original Message-
From: Eugen Block
Sent: mercredi, 6 mars 2024 10:47
To: ceph-users@ceph.io
Subject: [ceph-users] Re: Upgarde from 16.2.1 to 16.2.2 pacific stuck
There was another issue when having more than two MGRs, maybe you're
hitting that (https://tracker.ceph.com/issues/57675,
https
FAZENDA
Technical Support
Chemin du Curé-Desclouds 2, CH-1226 THONEX +41 (0)22 869 04 40
www.csti.ch
-Original Message-
From: Eugen Block
Sent: mercredi, 6 mars 2024 10:47
To: ceph-users@ceph.io
Subject: [ceph-users] Re: Upgarde from 16.2.1 to 16.2.2 pacific stuck
: [ceph-users] Re: Upgarde from 16.2.1 to 16.2.2 pacific stuck
Hi,
a couple of things.
First, is there any specific reason why you're upgrading from .1 to .2? Why not
directly to .15? It seems unnecessary and you're risking upgrading to a "bad"
version (I believe it was 16.2.7) if you're app
There was another issue when having more than two MGRs, maybe you're
hitting that (https://tracker.ceph.com/issues/57675,
https://github.com/ceph/ceph/pull/48258). I believe my workaround was
to set the global config to a newer image (target version) and then
deployed a new mgr.
Zitat
Hi,
a couple of things.
First, is there any specific reason why you're upgrading from .1 to
.2? Why not directly to .15? It seems unnecessary and you're risking
upgrading to a "bad" version (I believe it was 16.2.7) if you're
applying evey minor release. Or why not upgrading to Quincy or
The process has now started but I have the following error on mgr to the
second node
root@rke-sh1-1:~# ceph orch ps
NAME HOST PORTSSTATUS
REFRESHED AGE VERSION IMAGE ID CONTAINER ID
crash.rke-sh1-1 rke-sh1-1 running
