Volume operations should set task state

Bug #1275144 reported by Phil Day on 2014-01-31
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned

Bug Description

Volume attach/detach/swap should set task_state so that conflicting operations such as migrate can be blocked via the check_instance_state decorator.

This would also allow users can see slow operations are still in progress.

Phil Day (philip-day) on 2014-02-01
Changed in nova:
assignee: nobody → Phil Day (philip-day)
tags: added: volumes
Changed in nova:
importance: Undecided → Wishlist
Phil Day (philip-day) wrote :
Changed in nova:
status: New → In Progress
Joe Gordon (jogo) on 2014-02-07
Changed in nova:
importance: Wishlist → Low

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/71165
Reason: This has been in merge conflict since April, abandoning. Please restore and rebase if this is still a thing.

Sean Dague (sdague) on 2014-09-15
Changed in nova:
status: In Progress → Confirmed
assignee: Phil Day (philip-day) → nobody
Changed in nova:
assignee: nobody → Bartosz Fic (bartosz-fic)
Changed in nova:
assignee: Bartosz Fic (bartosz-fic) → nobody
Paul Murray (pmurray) on 2015-11-10
Changed in nova:
assignee: nobody → Paul Murray (pmurray)
Changed in nova:
assignee: Paul Murray (pmurray) → nobody
Paul Murray (pmurray) wrote :

Should have unassigned that before - sorry.

After discussion we decided not to address this immediately. The issue is that using task states will serialize volume attach/detach operations. At the moment multiple volume detach or attach operations can be done in parallel. We need to decide if we want to keep that or not.

Another solution would be to check running actions/tasks instead of a single task state.

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Low → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers