Thank you Eugen. Indeed the answer went to Spam :(
So thanks to David for his workaround, it worked like a charm. Hopefully these
patches can make it into the next pacific release.
‐‐‐ Original Message ‐‐‐
On Thursday, September 9th, 2021 at 2:33 PM, Eugen Block wrote:
> You must
No problem, and it looks like they will. Glad it worked out for you!
David
On Thu, Sep 9, 2021 at 9:31 AM mabi wrote:
>
> Thank you Eugen. Indeed the answer went to Spam :(
>
> So thanks to David for his workaround, it worked like a charm. Hopefully
> these patches can make it into the next
You must have missed the response to your thread, I suppose:
https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/YA5KLI5MFJRKVQBKUBG7PJG4RFYLBZFA/
Zitat von mabi :
Hello,
A few days later the ceph status progress bar is still stuck and the
third mon is for some unknown reason
Hello,
A few days later the ceph status progress bar is still stuck and the third mon
is for some unknown reason still not deploying itself as can be seen from the
"ceph orch ls" output below:
ceph orch ls
NAME PORTSRUNNING REFRESHED AGE PLACEMENT
alertmanager
I forgot to mention, the progress not updating is a seperate bug, you
can fail the mgr (ceph mgr fail ceph1a.guidwn in your example) to
resolve that. On the monitor side, I assume you deployed using labels?
If so - just remove the label from the host where the monitor did not
start, let it fully
This sounds a lot like: https://tracker.ceph.com/issues/51027 which is
fixed in https://github.com/ceph/ceph/pull/42690
David
On Tue, Sep 7, 2021 at 7:31 AM mabi wrote:
>
> Hello
>
> I have a test ceph octopus 16.2.5 cluster with cephadm out of 7 nodes on
> Ubuntu 20.04 LTS bare metal. I just
