No mechanism for drivers to update info on migrated volumes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Critical
|
John Griffith |
Bug Description
The migration workflow currently allows two possibilities:
1. The backend handle the migration
2. The Cinder host assists and does a general migration
The problem is that in most cases option 2 is going to be used, BUT there's currently no mechanism to communicate to the driver that it's objects are a part of a migration or that a migration has been completed and volume-id's have been swapped around. The swapping of ID's is something a big ugly IMO but nevertheless it's how the process works, and if we're going to go and change the ID of a volume after a creation we need to give drives some sort of notification that we've done this so that they can update their internal information, whether that be names, provider_locations etc.
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-1 → 2015.1.0 |
Relates to bug: 1381943