yahoo-eng-team team mailing list archive

[wanghao <wanghao749@xxxxxxxxxx>]

Public bug reported:

There is use case: we have two nova components（call them nova A and nova
B） and one cinder component. Attach a volume to an instance in nova A
and then services of nova A become abnormal. Because the volume also
want to be used in nova B, so using cinder api "force detach volume" to
free this volume. But when nova A is normal, nova can't detach this
volume from instance by using nova api "detach volume" , as nova check
the volume state must be "attached".

I think should we add "force detach" function to nova just like "attach"
and "detach", because if using force detach volume in cinder, there is
still some attach information in nova which can't be cleaned by using
nova api "detach".

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1297127

Title:
  nova can't detach volume after force detach in cinder

Status in OpenStack Compute (Nova):
  New

Bug description:
  There is use case: we have two nova components（call them nova A and
  nova B） and one cinder component. Attach a volume to an instance in
  nova A and then services of nova A become abnormal. Because the volume
  also want to be used in nova B, so using cinder api "force detach
  volume" to free this volume. But when nova A is normal, nova can't
  detach this volume from instance by using nova api "detach volume" ,
  as nova check the volume state must be "attached".

  I think should we add "force detach" function to nova just like
  "attach" and "detach", because if using force detach volume in cinder,
  there is still some attach information in nova which can't be cleaned
  by using nova api "detach".

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1297127/+subscriptions