Activity log for bug #1489304

Date Who What changed Old value New value Message
2015-08-27 07:18:36 Zhenyu Zheng bug added bug
2015-08-27 07:19:49 Zhenyu Zheng nova: assignee Zhenyu Zheng (zhengzhenyu)
2015-08-27 07:48:26 OpenStack Infra nova: status New In Progress
2015-08-27 09:27:04 Koji Iida bug added subscriber Koji Iida
2016-07-04 01:53:47 Zhenyu Zheng nova: importance Undecided Medium
2016-07-06 01:58:58 Zhenyu Zheng 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. 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.
2016-07-06 02:30:12 Zhenyu Zheng 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. 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.
2017-03-21 16:24:40 Maciej Szankin nova: status In Progress New
2017-03-21 16:24:47 Maciej Szankin nova: assignee Zhenyu Zheng (zhengzhenyu)
2017-06-05 06:11:58 Takashi NATSUME nova: status New Confirmed
2018-02-04 14:21:31 Ameed Ashour nova: assignee Ameed Ashour (ameeda)
2018-02-04 14:30:03 Ameed Ashour nova: assignee Ameed Ashour (ameeda)