Cinder backup - Volume metadata inconsistency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Confirmed
|
Medium
|
Unassigned |
Bug Description
After restoring a volume from backup, the metadata of target volume is same as source volume.
In the PowerMax driver we capture the device id of each volume in the metadata and 'copying' the target volumes metadata to the source will assign the incorrect device id to it
1. Created 2 volumes - non_boot_3 and non_boot_4.
2. Took a volume backup of non_boot_3.
3. Restored this backup to volume non_boot_4. The device ID of volume non_boot_3 is copied to non_boot_4. I think the device ID of non_boot_4 should not be changed.
The 2 volumes detail before restore. Please note that device IDs are 000F1 and 000F2 for the volumes.
| 819a7410-
| 59e40d21-
Created a backup for volume non_boot_3 as below.
| a8a3ebbe-
Restored the backup to non_boot_4 as below.
stack@dldv0089:~$ ovb restore a8a3ebbe-
+------
| Field | Value |
+------
| backup_id | a8a3ebbe-
| volume_id | 819a7410-
| volume_name | non_boot_4 |
+------
After restore, volume details as below. Please note that device ID is 000F1 for both the volumes.
| 819a7410-
| 59e40d21-
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: dellemc drivers powermax |
tags: |
added: backup-restore inconsistency metadata removed: dellemc drivers powermax |