Public bug reported:
Currently, when rebuilding an instance with volume attached, the Nova compute
manager will directly call
_detach_volume() which will skip the checks of volume status
(volume_api.check_detach) and setting the
volume to 'detaching' (volume_api.begin_detaching) at Cinder side. This is
different with the normal volume
detach process.
Besides, when rebuilding, we should only allow detaching the volume with in-use
status, volume in status
such as 'retyping' should not allowed.
** Affects: nova
Importance: Undecided
Assignee: Zhenyu Zheng (zhengzhenyu)
Status: New
** Changed in: nova
Assignee: (unassigned) => Zhenyu Zheng (zhengzhenyu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1489304
Title:
Lack of volume status checks when detaching volume in rebuild.
Status in OpenStack Compute (nova):
New
Bug description:
Currently, when rebuilding an instance with volume attached, the Nova compute
manager will directly call
_detach_volume() which will skip the checks of volume status
(volume_api.check_detach) and setting the
volume to 'detaching' (volume_api.begin_detaching) at Cinder side. This is
different with the normal volume
detach process.
Besides, when rebuilding, we should only allow detaching the volume with
in-use status, volume in status
such as 'retyping' should not allowed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1489304/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
