yahoo-eng-team team mailing list archive

[OpenStack Infra <1973765@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/842107
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/cd3264a07e047b589e4064855169c37f17343e60
Submitter: "Zuul (22348)"
Branch:    master

commit cd3264a07e047b589e4064855169c37f17343e60
Author: Fernando Royo <froyo@xxxxxxxxxx>
Date:   Tue May 17 15:32:24 2022 +0200

    Delete vip port if create_vip_port raise exception
    
    Sometimes on heavy load over Neutron, operations over
    neutron client could raise a NeutronClientException that
    could cover, e.g. a timeout. In those case, sometimes the
    request finish after the client timeout and we have
    leftover resource.
    
    create_vip_port is called from Octavia API just before
    the create LB request, if this call raise a timeout
    maybe the vip port is finally created and linked to a LB
    that is not going to be created, so we have this port
    unuse.
    
    This patch will try to remove the leftover port for those
    situations.
    
    Closes-Bug: #1973765
    Change-Id: Iad9839ce99d50b969924b3fe369301b6dfed369d


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1973765

Title:
  LB creation failed due to address already in use

Status in neutron:
  Fix Released

Bug description:
  While running a heavy load test, where create CRUD operations over
  load balancers and editing all pending items (listener/pool/member).
  We are getting error "IP_ADDRESS already allocated in subnet".
  Apparently because the address is being used by a Port for the load-
  balancer, but the load-balancer doesn't exist in a post error check.

  e.g. when create loadbalancer is sent we get this error from Octavia
  API:

  octavia.common.exceptions.ProviderDriverError: Provider 'ovn' reports
  error: IP address 172.30.125.1 already allocated in subnet
  beb4de56-a2b1-487b-9ab5-e10a0ad0d7ac

  
  [stack@undercloud ~]$ openstack port list | grep 172.30.125.1
  | 6a9c24a2-7907-4b5c-b406-f74ba5a05820 | ovn-lb-vip-22efa8a7-460c-443f-8f53-ac53929e8637                  | fa:16:3e:ea:e5:c4 | ip_address='172.30.125.1', subnet_id='beb4de56-a2b1-487b-9ab5-e10a0ad0d7ac'   | DOWN   |

  
  [stack@undercloud ~]$ openstack loadbalancer list --vip-port-id ovn-lb-vip-22efa8a7-460c-443f-8f53-ac53929e8637  
  [stack@undercloud ~]$

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