Hi,
> On 25 Jul 2024, at 00:12, Yuri Weinstein wrote:
>
> We're happy to announce the 4th release in the Reef series.
The repo of reef now returns 404
> GET /rpm-reef/el8/SRPMS/ HTTP/1.1
> Host: download.ceph.com
>
< HTTP/1.1 404 Not Found
If change the repo to previous version, the answer 20
Hi Yuri et al,
The email announcement includes the fix for 61948, but the linked blog
page omits it entirely.
Suggest adding that note to the blog page.
The language used also differs slightly between the two announcements.
email:
> We're happy to announce the 4th release in the Reef series.
bl
We're happy to announce the 4th release in the Reef series.
An early build of this release was accidentally exposed and packaged
as 18.2.3 by the Debian project in April. That 18.2.3 release should
not be used. The official release was re-tagged as v18.2.4 to avoid
further confusion.
v18.2.4 cont
Hello Alfredo, all,
On 24.07.24 1:05 PM, Alfredo Rezinovsky wrote:
Ceph dashboard offers me to upgrade to v18.2.4.
I can't find any information on 18.2.4.
The is no 18.2.4 inhttps://docs.ceph.com/en/latest/releases/
Not a tag inhttps://github.com/ceph/ceph
I don´t understand why there's a 18.2
What I read on the Slack channel is that the publication job got stuck late in
the day and the restart finished late. I'll guess they announce today the new
version.
Kind regards,
Sake
> Op 24-07-2024 13:05 CEST schreef Alfredo Rezinovsky :
>
>
> Ceph dashboard offers me to upgrade to v18.
It is very good to be able to use Ingress for service manager This
possibility of high availability for Ed Will this feature be added in the
next version or should it still be implemented manually?
___
ceph-users mailing list -- ceph-users@ceph.io
To uns
Ceph dashboard offers me to upgrade to v18.2.4.
I can't find any information on 18.2.4.
The is no 18.2.4 in https://docs.ceph.com/en/latest/releases/
Not a tag in https://github.com/ceph/ceph
I don´t understand why there's a 18.2.4 image and what's in it.
--
Alfrenovsky
Hi,
Thanks for you reply. I'm not sure what do you means by full sync. I tried
data/metadata sync init/run but nothing happened. I tried with a fresh cluster
but still can't make it work. Here is the sync status:
realm 26c6fd00-56f3-473f-8d9b-e583efb58a2b (multi-region)
zonegroup
