Bug 2069580 - Deleted members remain in ERROR status
Summary: Deleted members remain in ERROR status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z9
: 16.1 (Train on RHEL 8.2)
Assignee: Fernando Royo
QA Contact: Fiorella Yanac
URL:
Whiteboard:
Depends On: 2063978 2069587
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-29 08:13 UTC by Fernando Royo
Modified: 2022-12-07 20:26 UTC (History)
8 users (show)

Fixed In Version: python-networking-ovn-7.3.1-1.20220422083617.4e24f4c.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of: 2063978
Environment:
Last Closed: 2022-12-07 20:26:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 835216 0 None MERGED Fix deletion of members without subnet_id 2022-03-29 08:15:54 UTC
Red Hat Issue Tracker OSP-14378 0 None None None 2022-03-29 17:47:44 UTC
Red Hat Product Errata RHBA-2022:8795 0 None None None 2022-12-07 20:26:48 UTC

Description Fernando Royo 2022-03-29 08:13:53 UTC
+++ This bug was initially created as a clone of Bug #2063978 +++

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

stack@ubuntu2004:~/devstack$ openstack loadbalancer member create --name vm1 --address $IPVM01 --protocol-port 80 pool1
+---------------------+--------------------------------------+
| Field               | Value                                |
+---------------------+--------------------------------------+
| address             | 192.168.100.136                      |
| admin_state_up      | True                                 |
| created_at          | 2022-03-14T17:12:10                  |
| id                  | c8245713-ef5f-4278-8c03-b39d5cf7fbf0 |
| name                | vm1                                  |
| operating_status    | NO_MONITOR                           |
| project_id          | edcc48bd917e4d668ab6b9b892a40cb5     |
| protocol_port       | 80                                   |
| provisioning_status | PENDING_CREATE                       |
| subnet_id           | None                                 |
| updated_at          | None                                 |
| weight              | 1                                    |
| monitor_port        | None                                 |
| monitor_address     | None                                 |
| backup              | False                                |
| tags                |                                      |
+---------------------+--------------------------------------+

4. Try to delete the member created in 3.

stack@ubuntu2004:~/devstack$ openstack loadbalancer member delete pool1 vm1
stack@ubuntu2004:~/devstack$ openstack loadbalancer member list pool1
+--------------------------------------+------+----------------------------------+---------------------+-----------------+---------------+------------------+--------+
| id                                   | name | project_id                       | provisioning_status | address         | protocol_port | operating_status | weight |
+--------------------------------------+------+----------------------------------+---------------------+-----------------+---------------+------------------+--------+
| c8245713-ef5f-4278-8c03-b39d5cf7fbf0 | vm1  | edcc48bd917e4d668ab6b9b892a40cb5 | ERROR               | 192.168.100.136 |            80 | NO_MONITOR       |      1 |
+--------------------------------------+------+----------------------------------+---------------------+-----------------+---------------+------------------+--------+


Expected result:
Member is deleted correctly

Actual result:
Member keeps in ERROR state.

Comment 13 errata-xmlrpc 2022-12-07 20:26:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1.9 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8795


Note You need to log in before you can comment on or make changes to this bug.