Error volume status after detach a migrating volume
Bug #1483545 reported by
Wilson Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Confirmed
|
Undecided
|
TARUN KUMAR MAHTO |
Bug Description
When detach a volume which is 'in-use' and under migration, the detach progress goes successfully but after the detach progress is done, the status of the volume is still 'in-use', even after the migration is done. I have dug into the code and saw that the volume status won't be updated to 'available' after volume detached successfully because it's migrate_status is not None. I think this is a bug. If the status of the volume won't be updated to 'available' when it's migrate_status is not None, the cinder client should not let the user do the volume detach operation, or we should re-consider the volume status after the migration is done, instead of just leave it behind.
description: | updated |
description: | updated |
summary: |
- Status error after detach volume when it's under migration + Error volume status after detach a migrating volume |
tags: | added: migration |
Changed in cinder: | |
assignee: | nobody → TARUN KUMAR MAHTO (tarun1471) |
To post a comment you must log in.
This is part of the BP work in https:/ /blueprints. launchpad. net/cinder/ +spec/migration -improvement.
I am currently working on the migration termination when other actions come during the migration in process.(There is already a patch for it: https:/ /review. openstack. org/#/c/ 207754/)
The available volume is the first step to land. And next I will focus on the in-use volumes.