Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2263552

Summary:	Multiple listener-pool-member on IPv6 LB getting second pool in ERROR Edit
Product:	Red Hat OpenStack	Reporter:	Fernando Royo <froyo>
Component:	python-ovn-octavia-provider	Assignee:	Fernando Royo <froyo>
Status:	CLOSED ERRATA	QA Contact:	Bruna Bonguardo <bbonguar>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.2 (Train)	CC:	apevec, dhughes, ekuris, gthiemon, jamsmith, lhh, majopela, mariel, prgutier, scohen, tweining
Target Milestone:	z3	Keywords:	Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-ovn-octavia-provider-1.0.3-17.1.20231025110806.el9ost	Doc Type:	Bug Fix
Doc Text:	This update fixes a bug that prevented load-balancing of traffic on some Load-balancing service (octavia) pool members on IPv6 networks in an ML2/OVN environment. + Before this update, if you added a second `listener+pool+member` to a pool, the pool entered an ERROR state and traffic within that pool was not load-balanced. + With this update, traffic is load-balanced to all members as expected.	Story Points:	---
Clone Of:	2263550	Environment:
Last Closed:	2024-05-22 20:40:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2263550
Bug Blocks:

Description Fernando Royo 2024-02-09 17:05:09 UTC

+++ This bug was initially created as a clone of Bug #2263550 +++

Description of problem:
When an LB IPv6 is created using a bulk command or when multiple listener-pool-member are added sequentially, the second listener-pool managed fails when adding a member, resulting in the pool's state being in an ERROR state.

The error in traceback is:

2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver Traceback (most recent call last):
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver File "/usr/lib/python3.6/site-packages/networking_ovn/octavia/ovn_driver.py", line 1883, in member_create
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver self._add_member(member, ovn_lb, pool_key)
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver File "/usr/lib/python3.6/site-packages/networking_ovn/octavia/ovn_driver.py", line 1841, in _add_member
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver self._refresh_lb_vips(ovn_lb.uuid, external_ids)
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver File "/usr/lib/python3.6/site-packages/networking_ovn/octavia/ovn_driver.py", line 1051, in _refresh_lb_vips
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver vip_ips = self._frame_vip_ips(lb_external_ids)
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver File "/usr/lib/python3.6/site-packages/networking_ovn/octavia/ovn_driver.py", line 1039, in _frame_vip_ips
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver if netaddr.IPNetwork(lb_vip).version == 6:
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver File "/usr/lib/python3.6/site-packages/netaddr/ip/__init__.py", line 938, in __init__
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver raise AddrFormatError('invalid IPNetwork %s' % addr)
2024-02-07 12:40:56.166 13 ERROR networking_ovn.octavia.ovn_driver netaddr.core.AddrFormatError: invalid IPNetwork [fd2e:6f44:5dd8:c956::1a]

So apparently, the LB_VIP is enclosed in additional brackets [ ] when adding the member to the second listener-pool-member.


Version-Release number of selected component (if applicable):
RHOSP 16.2

How reproducible:


Steps to Reproduce:
1. Create a LB over a IPv6 with more than a listener-pool-member
2.
3.

Actual results:
Second pool keeps in ERROR state

Expected results:
LB created correctly

Comment 15 errata-xmlrpc 2024-05-22 20:40:37 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 17.1.3 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-2024:2741