yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

I think on the Nova side this is pretty much working as designed. If
there is different / better ironic behavior, perhaps it could be brought
up with the Ironic team?

** Changed in: nova
       Status: New => Opinion

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

Title:
  ironic does not clean or shutdown nodes if nova-compute is down at the
  moment of 'nova delete'

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Affected configuration: Ironic installation with Ironic driver for
  nova.

  If nova-compute service is down at the moment of execution 'nova
  delete' for instance, nova marks instance as 'deleted' even node is
  continue to run.

  Steps to reproduce:
  1. Prepare ironic/nova
  2. Start instance (nova boot/openstack server create)
  3. Wait until 'ACTIVE' state for instance.
  4. Stop nova-compute
  5. Wait until it become 'down' in 'nova service-list'
  5. Execute 'nova delete' command for instance.
  6. Start nova-compute serivce

  Expected result:
  - Instance sits in the 'deleting' state until nova-compute is not come back.
  - Node switch to 'cleaning/available' as soon as nova-compute come back
  - Tenant instance (baremetal server) stops to operate as soon as nova-compute is up.
  nova-compute is up.

  Actual result:
  - Instance deleted almost instantly regardless of nova-compute status.
  - Node keeps 'active' state with filled in 'Instance UUID' field.
  - Tenant instance (baremetal server) continue to work after nova-compute is up to "running_deleted_instance_action" time.

  I believe this is incorrect behavior, because it allows tenants to
  continue to use services regardless of nova report that there are no
  instances are allocated to tenant.

  Affected version: newton.

  P.S. Normally nova (with libvirt/kvm driver) would keep instance in
  'deleting' state until nova-compute is not come back, and remove it
  from server (from libvirt). Only after that nova marks instance as
  deleted in database. Ironic driver should do the same.

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