From 662b8210aab8e08bdddbf30e2b21ae357f3be32e Mon Sep 17 00:00:00 2001 From: Sofia Enriquez Date: Tue, 2 Jun 2020 19:31:34 +0000 Subject: [PATCH] Doc note warning about retyping an unencrypted/encrypted volume. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit As we discussed at Victoria PTG[1] it would be nice to have a note warning users to don’t try this. [1] https://wiki.openstack.org/wiki/CinderVictoriaPTGSummary#Sizing_encrypted_volumes Partial-Bug: #1687880 Change-Id: Ifa896c5f7336d3ce2a382ded9dcb4b3d595220db --- doc/source/contributor/migration.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/source/contributor/migration.rst b/doc/source/contributor/migration.rst index 86443a1f3b0..090083232b4 100644 --- a/doc/source/contributor/migration.rst +++ b/doc/source/contributor/migration.rst @@ -45,6 +45,13 @@ regardless if they are located on the same c-vol node or not. Scenario 2: Migration between two back-ends with different volume types, regardless if the back-ends are located on the same c-vol node or not. +.. note:: + Retyping an unencrypted volume to the same size encrypted volume will + most likely fail. Even though the volume is the same size as the source + volume, the encrypted volume needs to store additional encryption + information overhead. This results in the new volume not being large + enough to hold all data. + Please do not try this in older releases. How to do volume migration via CLI ----------------------------------