RemoteFS based drivers do not honor clone volume size
Bug #1554760 reported by
Sean McGinnis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Triaged
|
Medium
|
Unassigned |
Bug Description
It's possible to create a volume from a source volume with a different size. The create_
Changed in cinder: | |
milestone: | none → newton-2 |
Changed in cinder: | |
assignee: | nobody → Ji.Wei (jiwei) |
Changed in cinder: | |
assignee: | Ji.Wei (jiwei) → Erlon R. Cruz (sombrafam) |
status: | New → In Progress |
Changed in cinder: | |
milestone: | newton-2 → ocata-1 |
Changed in cinder: | |
milestone: | ocata-1 → ongoing |
Changed in cinder: | |
assignee: | Erlon R. Cruz (sombrafam) → Xinli Guan (xinli-v) |
To post a comment you must log in.
In remotefs drive, the code flow of create a clone volume is
1、Create a snapshot of the source volume
2、Call function: copy_volume_ from_snapshot _copy_volume_ from_snapshot( temp_snapshot,
volume_ info,
volume[ 'size'] )
self.
This function was introduced to the specified volume['size']
3、Delete temporary snapshot
From the code flow, it seems, do not need to check if it needs to extend the volume to a new size
However, the copy_volume_ from_snapshot is not implemented in the drive
def _copy_volume_ from_snapshot( self, snapshot, volume, volume_size): rror()
raise NotImplementedE
This causes the create_ volume_ from_snapshot create_ cloned_ volume function to be unable to use.
Perhaps, this requires a new BP to achieve this function?