← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1337461] Re: Race conditions with builds and deletes in Ironic driver

 

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  Race conditions with builds and deletes in Ironic driver

Status in Ironic:
  Invalid
Status in OpenStack Compute (nova):
  Expired

Bug description:
  While perhaps not officially supported by nova, when running 2 nova-
  computes for Ironic, you can get a delete to happen at the same time
  as a build.  The ironic virt driver for nova skips unprovision when
  the node is not in certain states...  It happens that unprovision is
  skipped when a Node is still deploying...   Nova then tries to unset
  the instance_uuid and ends up failing and retrying on a 409 until
  ironic finishes the build.  It then succeeds and you end up with a
  Node in ironic that is 'active' but has no instance_uuid.

  In addition to this, there's no provision_state checking in the virt
  driver when reporting resources to the compute manager. There's
  checking on if instance_uuid is assigned..  and if there's not one, it
  assumes the node is free.  In this case, it turns out the node is not
  really free... but somewhat orphaned.  Scheduling should probably skip
  these if they happen.

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