yahoo-eng-team team mailing list archive

[Elod Illes <1929886@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/victoria
       Status: Fix Committed => Fix Released

** Changed in: nova/wallaby
       Status: Fix Committed => 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/1929886

Title:
  [neutron]http_retries config option not used when calling the port
  binding API

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  New
Status in OpenStack Compute (nova) rocky series:
  New
Status in OpenStack Compute (nova) stein series:
  In Progress
Status in OpenStack Compute (nova) train series:
  In Progress
Status in OpenStack Compute (nova) ussuri series:
  In Progress
Status in OpenStack Compute (nova) victoria series:
  Fix Released
Status in OpenStack Compute (nova) wallaby series:
  Fix Released

Bug description:
  Discovered downstream [1] that the [neutron]http_retries config option
  has no effect on calls to the port binding API, so calls to it are not
  resilient like our other calls to the neutron API.

  The neutronclient didn't have support for the port binding API at the
  time when nova needed to call it, so a manual ksa client was created
  in the interim.

  When the [neutron]http_retries config option was added [2], this
  manual client was missed and thus never does any retries.

  The backportable fix for this will pass the CONF.neutron.http_retries
  option to the ksa client and the following proposed change to use the
  now existing neutronclient support should be reviewed and merged to
  prevent future similar bugs:

  https://review.opendev.org/c/openstack/nova/+/706295

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1955031
  [2] https://review.opendev.org/c/openstack/nova/+/712226

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