Comment 3 for bug 1450649

Thanks Vincent. I think John identified the root issue. This probably only impacts those drivers that use the volume ID as the identifier on the backend. So we probably either need to update those drivers to not use ID, or use his suggestion to have an update call to give those drivers a chance to update their internal information to be able to correctly locate the new volume.

I could see having a call like update_voume_info() being useful for other purposes in the future, so my inclination is to go that direction.