Frédéric's policy below I think is very good advice. The only reason to
upgrade sooner than his advice is when you need a missing feature or fear
hitting a fixed bug -- or just like living on the edge.
On 4/19/25 16:45, Frédéric Nass wrote:
Hi e3gh75 :-)
There's no dumb questions. Here's a sum up of what I've learned:
- You can skip point releases in the same major version (18.2.2 -> 18.2.4).
- You can skip minor releases in the same major version (18.0.1 -> 18.2.2).
- You can skip one major release (at max) while also skipping minor releases and point
releases (17.1.1 -> 19.2.2) but it's always better to upgrade to the latest major
release (major+minor+point) before upgrading to the latest up-to-date major release
(17.1.1 -> 17.2.8 -> 19.2.2).
Regarding major releases, you can go from Pacific (16) to Reef (18) or Quincy
(17) to Squid (19) without concerns.
Choosing a stable release (x.2.z) is always preferable to x.0.z and x.1.z.
Waiting 3-4 weeks to jump to the latest point release is also good practice.
Regards,
.
----- Le 18 Avr 25, à 18:21, e3g...@gmail.com a écrit :
Hello,
I have dumb question but hopefully simple question. In the cephadm documentation
it states you can upgrade from a point release to another point release without
problem, 15.2.2 to 15.2.3. What about jumping up a version or two, like from
18.2.4 to 19.2.2? What have others experience been? Any advice? Thank you for
your time.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
