yahoo-eng-team team mailing list archive

[Vladyslav Drok <vdrok@xxxxxxxxxxxx>]

Moved this to nova, as the fix is actually there.

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

** Changed in: ironic
       Status: New => Won't Fix

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

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

Title:
  Ironic Nova Virt driver tries to act on exclusively locked node during
  tear down

Status in Ironic:
  Won't Fix
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  When a node is unprovisioned with cleaning enabled it moves into the
  CLEANING state which exclusively locks the node.

  A node will remain in CLEANING state and therefore locked until the node
  moves into the CLEAN_WAIT state, this can take as long as it takes to
  decommission the node and power it back on for booting the cleaning
  ramdisk. This can take a surprisingly long amount of time with real
  hardware.

  There are several tasks that require a lock on the Ironic node,
  which it can't claim if the node is already exclusively locked by being
  in the CLEANING state.

  This means that people deploying nova have to tune their nova timeouts
  and retries to match their equipment, to ensure that nova keeps
  retrying until that node becomes unlocked. This can slow down the turn
  around time of Ironic nodes and confuses users wondering why their
  node is taking so much time to delete.

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