Bug 1956427

Summary: [Doc] RBD volume created from snapshot on encrypted volume cannot be used
Product: Red Hat OpenStack Reporter: Sofia Enriquez <senrique>
Component: documentationAssignee: Alex McLeod <amcleod>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16.0 (Train)CC: gcharot
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 16:03:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sofia Enriquez 2021-05-03 16:36:00 UTC 
This bug was initially created as a copy of Bug #1772531

I am copying this bug because: we need to add some warning in the documentation.

[RBD only bug] 

Creating a volume from a snapshot of an encrypted volume may result in an unusable volume.
Detectable only by looking at behaviour inside the instance upon attach.

Creating encrypted volume from a snapshot -created from a
source encrypted volume as well- will be forced to resize and  lose the encrypted header.

When creating an encrypted volume from a snapshot of an encrypted volume, if the amount
of data in the original volume at the time the snapshot was created is very close to the
gigabyte boundary given by the volume's size, it is possible for the data in the new
volume to be silently truncated.