When cloning encrypted volumes, Cinder could change the volume's encryption key rather than re-using the same key.
Pushing to 17, upstream dev will continue during the train cycle
Verified on: openstack-cinder-15.0.1-0.20191128040416.ef025a7.el8ost.noarch Works as expected, manual testing to be automated ASAP.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0283