** Also affects: nova/pike
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/queens
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => In Progress
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/ocata
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/pike
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/queens
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/ocata
Importance: Undecided => Medium
--
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/1662867
Title:
update_available_resource_for_node racing instance deletion
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) ocata series:
In Progress
Status in OpenStack Compute (nova) pike series:
New
Status in OpenStack Compute (nova) queens series:
New
Bug description:
Description
===========
The following trace was seen multiple times during a CI run for
https://review.openstack.org/#/c/383859/ :
http://logs.openstack.org/09/395709/7/check/gate-tempest-dsvm-full-devstack-plugin-nfs-nv/a4c1057/logs/screen-n-cpu.txt.gz?level=ERROR#_2017-02-07_19_10_25_548
http://logs.openstack.org/09/395709/7/check/gate-tempest-dsvm-full-devstack-plugin-nfs-nv/a4c1057/logs/screen-n-cpu.txt.gz?level=ERROR#_2017-02-07_19_15_26_004
In the first example a request to terminate the instance 60b7cb32
appears to race an existing run of the
update_available_resource_for_node periodic task :
req-fa96477b-34d2-4ab6-83bf-24c269ed7c28
http://logs.openstack.org/09/395709/7/check/gate-tempest-dsvm-full-
devstack-plugin-nfs-
nv/a4c1057/logs/screen-n-cpu.txt.gz?#_2017-02-07_19_10_25_478
req-dc60ed89-d3da-45f6-b98c-8f57c767d751
http://logs.openstack.org/09/395709/7/check/gate-tempest-dsvm-full-
devstack-plugin-nfs-
nv/a4c1057/logs/screen-n-cpu.txt.gz?#_2017-02-07_19_10_25_548
Steps to reproduce
==================
Delete an instance while update_available_resource_for_node is running
Expected result
===============
Either swallow the exception and move on or lock instances in such a way that
they can't be removed while this periodic task is running.
Actual result
=============
update_available_resource_for_node fails and stops.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
https://review.openstack.org/#/c/383859/ - but it should reproduce
against master.
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
Libvirt
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/1662867/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
