Bug 2087196 - LB creation failed due to address already in use
Summary: LB creation failed due to address already in use
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: z9
: 16.1 (Train on RHEL 8.2)
Assignee: Fernando Royo
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On: 2080434 2087204 2133537
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-17 14:36 UTC by Fernando Royo
Modified: 2022-12-07 20:26 UTC (History)
9 users (show)

Fixed In Version: python-networking-ovn-7.3.1-1.20220810153841.4e24f4c.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of: 2080434
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 842107 0 None MERGED Delete vip port if create_vip_port raise exception 2022-08-10 11:40:36 UTC
Red Hat Issue Tracker OSP-15276 0 None None None 2022-05-17 15:00:48 UTC
Red Hat Product Errata RHBA-2022:8795 0 None None None 2022-12-07 20:26:48 UTC

Comment 6 Itzik Brown 2022-11-14 08:57:51 UTC 
1. Ran installation with Kuryr on top of OSP16.1
2. Exported the variables (export WORKLOAD=cluster-density; export JOB_ITERATIONS=40)
3. Ran https://github.com/cloud-bulldozer/e2e-benchmarking/blob/master/workloads/kube-burner/run.sh

There were messages like
IP address 172.30.150.216 already allocated in subnet e9494f07-b4d2-49c1-b673-08e6d7970c14

But it seems that the LB was created

Checked with 
OSP RHOS-16.1-RHEL-8-20221108.n.1
OCP 4.11.0-0.nightly-2022-11-08-222031
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.