File: fix-backup-handling-of-encryption-key-id-f2fa56cadd80d582.yaml

package info (click to toggle)
cinder 2%3A17.0.1-1%2Bdeb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 36,796 kB
  • sloc: python: 395,277; pascal: 2,085; sh: 585; makefile: 111; xml: 26; sql: 5
file content (13 lines) | stat: -rw-r--r-- 598 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
---
fixes:
  - |
    Fix the way encryption key IDs are managed for encrypted volume backups.
    When creating a backup, the volume's encryption key is cloned and assigned
    a new key ID. The backup's cloned key ID is now stored in the backup
    database so that it can be deleted whenever the backup is deleted.

    When restoring the backup of an encrypted volume, the destination volume
    is assigned a clone of the backup's encryption key ID. This ensures every
    restored backup has a unique encryption key ID, even when multiple volumes
    have been restored from the same backup.