diff options
| author | Sean McGinnis <sean.mcginnis@gmail.com> | 2018-04-04 14:56:27 -0500 |
|---|---|---|
| committer | Sean McGinnis <sean.mcginnis@gmail.com> | 2018-10-26 12:02:58 -0500 |
| commit | f00ffebea61f94f2334d1c1578bc23986bbcf58c (patch) | |
| tree | ac8c82b5d0aa18087cd4a6a1a5fa30eb2005f58b /openstackclient/api | |
| parent | 06263bd5852aad9cd03a76f50140fbbb2d0751ba (diff) | |
| download | python-openstackclient-f00ffebea61f94f2334d1c1578bc23986bbcf58c.tar.gz | |
Remove invalid 'unlock-volume' migration arg
There is an optional flag that can be passed in to a
volume migration to tell Cinder to 'lock' a volume so
no other process can abort the migration. This is
reflected correctly with the --lock-volume argument
flag to `openstack volume migrate`, but there is
another --unlock-volume flag that is shown in the help
text for this command that does not do anything and is
not used anywhere.
Since there is no action to "unlock" a volume, this
just causes confusion - including for Cinder developers
that know this API. To avoid confusion, this invalid
flag should just be removed from the command.
Change-Id: I5f111ed58803a1bf5d34e828341d735099247108
Diffstat (limited to 'openstackclient/api')
0 files changed, 0 insertions, 0 deletions