yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1208638] Re: baremetal PXE timeout interrupts active deploys

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Devananda van der Veen <1208638@xxxxxxxxxxxxxxxxxx>
Date: Mon, 20 Jan 2014 23:46:40 -0000
Reply-to: Bug 1208638 <1208638@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This doesn't affect Ironic as we don't (currently) have a timeout
mechanism for deploys (which is another issue unto itself) and our state
tracking is different than Nova's, so once we add operation-timeouts at
a higher level, it'll be accounted for.

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

Title:
  baremetal PXE timeout interrupts active deploys

Status in Ironic (Bare Metal Provisioning):
  Invalid
Status in OpenStack Compute (Nova):
  Triaged

Bug description:
  When the DD of an image takes an unexpectedly long time (e.g. due to
  network congestion), the PXE deploy timeout may interrupt the deploy
  by powering off the node, which then causes it to be rescheduled and
  exacerbates the problem.

  If we monitor dd and check it is making progress, we could use this as
  a heartbeat to prevent inappropriate interrupts - and have the timeout
  look for a period of no progress (vs just absolute time).

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