yahoo-eng-team team mailing list archive

[Dmitriy Rabotyagov <1932326@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========

In case, when some request (ie instance shutdown) is sent to the compute
that is not available, request continue hanging in queue. In the
meanwhile, instance can be evacuated from this host to the new available
compute. However once original compute host becomes available again it
process all messages waiting for it in queue without extra verification,
which results in super delayed request being processed (ie instance goes
shut down on new compute) even if this host doesn't own resource
anymore.

Steps to reproduce
==================

1. compute1 goes down
2. Send shutdown request to the VM that is hosted on compute1
3. Evacuate VM (it would require state reset ATM - related bug #1932126) to compute2
4. boot compute1
5. compute1 will make instance that is currently working on compute2 to shutdown

Expected result
===============

Compute1 that does not own resource anymore should not be able to
influence it

Environment
===========

SHA: c7d9d6d9dd25e21ec76ceea294cdf1690686a086 (Victoria)
Hypervisor: KVM
Networking: ovs
Storage: Ceph

** 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/1932326

Title:
  Compute process cast against instance it does not own

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========

  In case, when some request (ie instance shutdown) is sent to the
  compute that is not available, request continue hanging in queue. In
  the meanwhile, instance can be evacuated from this host to the new
  available compute. However once original compute host becomes
  available again it process all messages waiting for it in queue
  without extra verification, which results in super delayed request
  being processed (ie instance goes shut down on new compute) even if
  this host doesn't own resource anymore.

  Steps to reproduce
  ==================

  1. compute1 goes down
  2. Send shutdown request to the VM that is hosted on compute1
  3. Evacuate VM (it would require state reset ATM - related bug #1932126) to compute2
  4. boot compute1
  5. compute1 will make instance that is currently working on compute2 to shutdown

  Expected result
  ===============

  Compute1 that does not own resource anymore should not be able to
  influence it

  Environment
  ===========

  SHA: c7d9d6d9dd25e21ec76ceea294cdf1690686a086 (Victoria)
  Hypervisor: KVM
  Networking: ovs
  Storage: Ceph

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