Remove force check from copy_volume_to_image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Low
|
Unassigned |
Bug Description
https:/
commit fb2c434c2461a25
Author: John Griffith <email address hidden>
Date: Wed Apr 22 04:28:34 2015 +0000
Remove force check from copy_volume_
The upload_
upload a volume even though the volume is attached/in-use. A user can
get away with this with the LVM driver because the LVM backing is
local to the Cinder worker node that's pushing the bits to Glance.
The problem is, this only works for local storage, it won't work
with any iSCSI devices because they can't do multi-attach. Also,
the reason we required that a volume NOT be in-use for this
operation is because we have no way of keeping the guest Instance
from writing to the volume while we're uploading, and corrupting the data.
This has been exposed like this for several releases, so removing it
now likely would not be a good user experience. Instead, this
patch add a config option to enable/disable it (default is to
disable), and deployers can choose whether they would like to
allow the use of --force True or not.
DocImpact Disables the --force option to copy-volume-
Change-Id: I1210186689dea2
Closes-Bug: 1446954
Changed in openstack-manuals: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in openstack-manuals: | |
assignee: | nobody → jelly (coding1314) |
Changed in openstack-manuals: | |
assignee: | jelly (coding1314) → Gauvain Pocentek (gpocentek) |
status: | Triaged → In Progress |
Changed in openstack-manuals: | |
assignee: | Gauvain Pocentek (gpocentek) → nobody |
The option name is 'enable_ force_upload' .