Can't restore volume to a different type than the snapshot
Bug #1289931 reported by
Cory Stone
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith |
Bug Description
There is now a volume_type_id on the snapshot model and you cannot create a volume from that snapshot as any other type. It changes the type of the volume to the one on the snapshot.
This is complicated by the fact that the migration that added this column didn't insert any data into this column for any existing snapshots, so they have a NULL volume_type_id value.
Changed in cinder: | |
importance: | Undecided → High |
milestone: | none → icehouse-rc1 |
Changed in cinder: | |
assignee: | nobody → John Griffith (john-griffith) |
Changed in cinder: | |
milestone: | icehouse-rc1 → none |
Changed in cinder: | |
milestone: | juno-3 → juno-rc1 |
Changed in cinder: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-1 → 7.0.0 |
To post a comment you must log in.
Re the migration being broken, yuck.
I don't think you should be able to create a volume from a snapshot of a different type - snapshots are lightweight, let's keep them that way? We can't provide both an abstraction of fundamentally different storage types and a 100% feature matrix if we allow every conceivable operation. This should be done with a create and a retype IMO