yahoo-eng-team team mailing list archive

[Arne Wiebalck <1884217@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

When an instance is deleted, it seems that Nova calls back into
Placement and the corresponding resource provider becomes available
again right away. For Ironic instances, the deletion is not
instantaneous, however, and the node is not available at this point.
Instance creation will hence fail. This is fixed once the resource
tracker comes along and corrects the information in placement, but with
hundreds of nodes and the way the resource tracker handles them, this
leaves a window of several minutes.

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

Delete an instance and compare the state of the resource provider in
placement with the provision state of the node:

# openstack baremetal node show --fit c55cb55d-46bb-404f-948e-f777fdef99ce --fields provision_state
+-----------------+------------+
| Field           | Value      |
+-----------------+------------+
| provision_state | clean wait |
+-----------------+------------+
# OS_PLACEMENT_API_VERSION=1.10 openstack allocation candidate list --resource CUSTOM_BAREMETAL_P1_xyz_S6045_C6_abc='1'
+---+------------------------------------------------+--------------------------------------+--------------------------------------------------+
| # | allocation                                     | resource provider                    | inventory used/capacity                          |
+---+------------------------------------------------+--------------------------------------+--------------------------------------------------+
| 1 | CUSTOM_BAREMETAL_P1_CD5795986_S6045_C6_IP104=1 | c55cb55d-46bb-404f-948e-f777fdef99ce | CUSTOM_BAREMETAL_P1_xyz_S6045_C6_abc=0/1 |
+---+------------------------------------------------+--------------------------------------+--------------------------------------------------+

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

The resource provider should not become available in placement before
the Ironic node moved to provision state available.


Actual result
=============

The resource provider is available in placement while the Ironic node is
not in provision state available yet.


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

Ironic on Train, Nova on Stein

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

Title:
  Nova informs Placement too early upon Ironic instance deletion

Status in OpenStack Compute (nova):
  New

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

  When an instance is deleted, it seems that Nova calls back into
  Placement and the corresponding resource provider becomes available
  again right away. For Ironic instances, the deletion is not
  instantaneous, however, and the node is not available at this point.
  Instance creation will hence fail. This is fixed once the resource
  tracker comes along and corrects the information in placement, but
  with hundreds of nodes and the way the resource tracker handles them,
  this leaves a window of several minutes.

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

  Delete an instance and compare the state of the resource provider in
  placement with the provision state of the node:

  # openstack baremetal node show --fit c55cb55d-46bb-404f-948e-f777fdef99ce --fields provision_state
  +-----------------+------------+
  | Field           | Value      |
  +-----------------+------------+
  | provision_state | clean wait |
  +-----------------+------------+
  # OS_PLACEMENT_API_VERSION=1.10 openstack allocation candidate list --resource CUSTOM_BAREMETAL_P1_xyz_S6045_C6_abc='1'
  +---+------------------------------------------------+--------------------------------------+--------------------------------------------------+
  | # | allocation                                     | resource provider                    | inventory used/capacity                          |
  +---+------------------------------------------------+--------------------------------------+--------------------------------------------------+
  | 1 | CUSTOM_BAREMETAL_P1_CD5795986_S6045_C6_IP104=1 | c55cb55d-46bb-404f-948e-f777fdef99ce | CUSTOM_BAREMETAL_P1_xyz_S6045_C6_abc=0/1 |
  +---+------------------------------------------------+--------------------------------------+--------------------------------------------------+

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

  The resource provider should not become available in placement before
  the Ironic node moved to provision state available.

  
  Actual result
  =============

  The resource provider is available in placement while the Ironic node
  is not in provision state available yet.

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

  Ironic on Train, Nova on Stein

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