From dc6388b6fd3d55490cb7b6b4bb5c1b52b9daf716 Mon Sep 17 00:00:00 2001 From: tushargite96 Date: Thu, 27 Jan 2022 12:57:52 +0530 Subject: [PATCH] Update volume delete api-ref This patch update volume delete section in api-ref to understand preconditions more correctly Partial-Bug: #1918932 Change-Id: Icb5b4da3423555cd2ab0f5ee6d1dc881fc782484 --- api-ref/source/v3/volumes-v3-volumes.inc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/api-ref/source/v3/volumes-v3-volumes.inc b/api-ref/source/v3/volumes-v3-volumes.inc index 86777887e3c..91b57a55b9a 100644 --- a/api-ref/source/v3/volumes-v3-volumes.inc +++ b/api-ref/source/v3/volumes-v3-volumes.inc @@ -507,9 +507,13 @@ Preconditions - Volume status must be ``available``, ``in-use``, ``error``, ``error_restoring``, ``error_extending``, ``error_managing``, - and must not be migrating, attached, belong to a group or have snapshots. + and must not be ``migrating``, ``attached``, ``awaiting-transfer``, + belong to a group, have snapshots or be disassociated from + snapshots after volume transfer. -- You cannot already have a snapshot of the volume. +- The ``cascade`` option can be passed in the request if you want + all snapshots of this volume to be deleted automatically, + which should allow the volume deletion to succeed. - You cannot delete a volume that is in a migration.