yahoo-eng-team team mailing list archive

[Fernando Royo <1964817@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

An OVN provider Load Balancer allows the creation of members without
specifying the subnet-id. The internal logic allows OVN provider to
create the member by associating it with the subnet-id of the pool to
which it belongs, but the member is stored in Octavia DB without a
reference to the subnet_id associated with the pool.

Subsequently, when an attempt is made to delete a member that was
created without specifying the subnet_id to which it belongs, it is left
in an ERROR state, while a member that did include that parameter at
creation time is deleted correctly.

Steps to Reproduce:
1. Create a load balancer with OVN as provider
2. Create a listener and a pool associated to LB create in 1.
3. Create a member without parameter subnet-id
4. Try to delete the member created in 3.

Expected result:
Member is deleted correctly

Actual result:
Member keeps in ERROR state.

** Affects: neutron
     Importance: Undecided
     Assignee: Fernando Royo (froyoredhat)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Fernando Royo (froyoredhat)

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

Title:
  [ovn-octavia-provider] Deleted members remain in ERROR status

Status in neutron:
  New

Bug description:
  An OVN provider Load Balancer allows the creation of members without
  specifying the subnet-id. The internal logic allows OVN provider to
  create the member by associating it with the subnet-id of the pool to
  which it belongs, but the member is stored in Octavia DB without a
  reference to the subnet_id associated with the pool.

  Subsequently, when an attempt is made to delete a member that was
  created without specifying the subnet_id to which it belongs, it is
  left in an ERROR state, while a member that did include that parameter
  at creation time is deleted correctly.

  Steps to Reproduce:
  1. Create a load balancer with OVN as provider
  2. Create a listener and a pool associated to LB create in 1.
  3. Create a member without parameter subnet-id
  4. Try to delete the member created in 3.

  Expected result:
  Member is deleted correctly

  Actual result:
  Member keeps in ERROR state.

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