← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1909120] Re: n-api should reject requests to detach a volume when the compute is down

 

updating this to fix release sicne
https://review.opendev.org/c/openstack/nova/+/768352 is merged on master

backports have been propsoed to u and v so i have add those and i also
added train since i assume we want this in Train downstream?

if this need to go back futher then feel free to add those too but i
tred to pick a resonable set of branches.

** Also affects: nova/ussuri
   Importance: Undecided
       Status: New

** Also affects: nova/victoria
   Importance: Undecided
       Status: New

** Also affects: nova/train
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: Confirmed => Fix Released

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

Title:
  n-api should reject requests to detach a volume when the compute is
  down

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) train series:
  New
Status in OpenStack Compute (nova) ussuri series:
  New
Status in OpenStack Compute (nova) victoria series:
  New

Bug description:
  Description
  ===========
  At present requests to detach volumes from instances on down computes are accepted by n-api but will never be acted upon if the n-cpu service hosting the instance is down.

  n-api should reject such requests with a simple 409 HTTP conflict.

  Steps to reproduce
  ==================
  * Attempt to detach a volume from an instance residing on a down compute.

  Expected result
  ===============
  Request rejected by n-api

  Actual result
  =============
  Request accepted but never completed

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     Master

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

     libvirt + QEMU/KVM

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

     N/A

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

     N/A

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


References