From ad12da27cc2ee93dadba817e3195a46723a9ee54 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Thu, 1 Dec 2022 17:27:16 +1000 Subject: [PATCH] doc/cephadm - remove "danger" admonition Remove the "Danger!" admonition that warned against upgrading to Pacific from an older version of Ceph. That admonition was meant to protect against the issue discussed here: https://tracker.ceph.com/issues/53062. That issue was fixed in this PR: https://github.com/ceph/ceph/pull/43793. Signed-off-by: Zac Dover --- doc/cephadm/upgrade.rst | 23 ----------------------- 1 file changed, 23 deletions(-) diff --git a/doc/cephadm/upgrade.rst b/doc/cephadm/upgrade.rst index f4d7e87c3e52c..e0a9f610ae2a8 100644 --- a/doc/cephadm/upgrade.rst +++ b/doc/cephadm/upgrade.rst @@ -2,29 +2,6 @@ Upgrading Ceph ============== -.. DANGER:: DATE: 01 NOV 2021. - - DO NOT UPGRADE TO CEPH PACIFIC FROM AN OLDER VERSION. - - A recently-discovered bug (https://tracker.ceph.com/issues/53062) can cause - data corruption. This bug occurs during OMAP format conversion for - clusters that are updated to Pacific. New clusters are not affected by this - bug. - - The trigger for this bug is BlueStore's repair/quick-fix functionality. This - bug can be triggered in two known ways: - - (1) manually via the ceph-bluestore-tool, or - (2) automatically, by OSD if ``bluestore_fsck_quick_fix_on_mount`` is set - to true. - - The fix for this bug is expected to be available in Ceph v16.2.7. - - DO NOT set ``bluestore_quick_fix_on_mount`` to true. If it is currently - set to true in your configuration, immediately set it to false. - - DO NOT run ``ceph-bluestore-tool``'s repair/quick-fix commands. - Cephadm can safely upgrade Ceph from one bugfix release to the next. For example, you can upgrade from v15.2.0 (the first Octopus release) to the next point release, v15.2.1. -- 2.39.5