Description of problem: When migrating encryption keys based on the ConfKeyManager's fixed_key to Barbican, entries in the Cinder backup table need to be migrated. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create an encrypted volume using the ConfKeyManager 2. Create a backup of the volume 3. Update the deployment to Barbican and perform the Barbican key migration procedure Actual results: The encrypted volume's entry in the Backup table will still reference the all-zeros encryption_key_id associated with the ConfKeyMgr Expected results: The Backup table entry will have a Barbican encryption_key_id (not all zeros) Additional info: This issue has been fixed in stable/queens, and this BZ is to track testing the fix for OSP-13.
Verified RPM package version # docker exec -ti openstack-cinder-volume-docker-0 bash -c "rpm -q openstack-cinder" openstack-cinder-12.0.1-0.20180418194613.c476898.el7ost.noarch Verified according to steps describes in the bug description: 1. Create an encrypted volume using the ConfKeyManager 2. Create a backup of the volume 3. Update the deployment to Barbican and perform the Barbican key migration procedure
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-2018:2086