From a1d6e2b9fd9476d0b1bf02c2f3b50be39763a8bd Mon Sep 17 00:00:00 2001 From: Ngairangbam Mili Date: Mon, 29 Sep 2025 04:26:13 +0000 Subject: [PATCH] Update lvm snapshot documentation with invalid state Story: 2011394 Task: 52864 Change-Id: Ife683888c212e363e1701351135e3098c6338499 Signed-off-by: Ngairangbam Mili --- ...on-platform-software-updates-upgrades-06d6de90bbd0.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/source/updates/kubernetes/introduction-platform-software-updates-upgrades-06d6de90bbd0.rst b/doc/source/updates/kubernetes/introduction-platform-software-updates-upgrades-06d6de90bbd0.rst index 40f4db4e8..3dd1f415d 100644 --- a/doc/source/updates/kubernetes/introduction-platform-software-updates-upgrades-06d6de90bbd0.rst +++ b/doc/source/updates/kubernetes/introduction-platform-software-updates-upgrades-06d6de90bbd0.rst @@ -83,6 +83,14 @@ option can be used to take a snapshot of the main logical volumes at the start of deployment, such that in case of a rollback, the |LVM| snapshots can be restored in order to speed up the overall rollback procedure. +.. note:: + + Snapshots are created with a size that determines its capacity to track the + changes in the corresponding logical volume. When a snapshot reaches its + maximum capacity, the snapshot becomes invalid and cannot be restored. In + this case, the system will automatically fall back to the standard rollback + procedure. + For a Patch Release only, a **removal or un-deployment of a release** is supported. One or more Patch Releases can be removed/un-deployed by deploying a previous Patch Release.