snapshot-manage imports snapshots with wrong size
Bug #1623596 reported by
Adriano
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Michael Dovgal |
Bug Description
The manage snapshots feature does not import the snapshots with their real size.
E.g. When managing a snapshot of a volume that was extended after the snapshot was unmanaged, the snapshot will be imported to Cinder with the new volume size.
Steps to reproduce:
1- Create a volume v1 with 10 Gb
2- Create a snapshot s1 from v1
3- Unmanage the snapshot s1
4- Extend the volume v1 to 15 Gb
5- Manage s1
Result:
The snapshot is imported to Cinder with the volume size (15 Gb).
Expected:
The snapshot is imported to Cinder with its real size (10 Gb).
Note: In the example, the snapshot size on backend is still 10 Gb also.
Changed in cinder: | |
assignee: | nobody → Michael Dovgal (mdovgal) |
status: | New → Confirmed |
To post a comment you must log in.
hi, unfortunately, i was not able recreate the issue. when i try to unmanage a snapshot, it is removed from the snapshot list as if it was deleted (deleted status in DB). i am not sure how i can re-manage it, or if it was ever in the managed state. When i try to manually manage a snapshot by the command "cinder snapshot-manage <volume> <existing_ snapshot> ", it'd return a new snapshot creation process with error status. maybe someone with more experience can comment on this.