yahoo-eng-team team mailing list archive

["Dmitry \"Divius\" Tantsur" <divius.inside@xxxxxxxxx>]

Hi Chris, could you give status update on this bug? The patch seems
abandoned and also should be moved to Nova.

** Summary changed:

- race conditions with builds and deletes
+ Race conditions with builds and deletes in Ironic driver

** Also affects: nova
   Importance: Undecided
       Status: New

** Tags added: ironic

** Changed in: ironic
       Status: In Progress => Invalid

-- 
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 OpenStack Bare Metal Provisioning Service (Ironic):
  Invalid
Status in OpenStack Compute (Nova):
  New

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