Remove_image maybe throw ImageBusy exception

Bug #1628448 reported by coolias
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Undecided
Unassigned

Bug Description

In my test, found when in import image, config drive image maybe failed and throw ImageBusy exception

This often occured in nova host-evacuate test scenario.
In order to get vm ha, when compute node down, we need evacuate all instances from this node to the other.
how to reproduce:
1. create 50 instances with config driver disk in node1
2. unplug the ceph network cable of this node
3. do host-evacuate for this node
4. watch all the instances status, maybe failed because of this bug

I think, it is because the config driver disk still in use in ceph, so we need to caputure the ImageBusy exception and add retry logic

coolias (coolias-lj)
Changed in nova:
assignee: nobody → coolias (coolias-lj)
LeoZhang (zealoussnow)
Changed in nova:
status: New → Confirmed
coolias (coolias-lj)
Changed in nova:
status: Confirmed → In Progress
Revision history for this message
coolias (coolias-lj) wrote :
coolias (coolias-lj)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/378501
Reason: This patch has been sitting unchanged for more than 12 weeks. I am therefore going to abandon it to keep the review queue sane. Please feel free to restore the change if you're still working on it.

Revision history for this message
Sean Dague (sdague) wrote :

There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.

Changed in nova:
status: In Progress → Confirmed
assignee: coolias (coolias-lj) → nobody
Revision history for this message
Hongquan Zhu (zhuhq) wrote :

I found the same problem in my mitaka version. It dose not happen every time. So I feel that maybe the connection between config drive is not disconnected from instance, it shows busy status.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.