yahoo-eng-team team mailing list archive

[jichenjc <jichenjc@xxxxxxxxxx>]

Allow retrying network allocations separately

    Introduce a new config option, 'network_allocate_retries', that allows
    one to retry network allocations.  The default is 0 for no retries to
    match the current behavior.

    The network allocations currently get retried by a full retry of a build
    via the scheduler, if those are enabled.  This patch reduces the need to
    re-schedule for simple network allocation issues.

    The retrying happens in the network alloc async greenthread, so for virt
    drivers that support the new NetworkModel, the retrying potentially
    happens in the background while the image is being downloaded, etc.

** Changed in: nova
       Status: Triaged => Fix Released

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

Title:
  _build_instance does not have a recoverable
  network_api.allocate_for_instance

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  It appears that if the allocate of a instances network fails due to a
  race condition at the network_api layer that the instance will be set
  in the error state instead of trying to recover from said failure in a
  graceful manner (retrying could be one solution for example).  Looking
  at the NetworkManager code it if a race happens at the code level,
  then an exception will be passed back which will stop the instance
  from continuing to build.

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