Bug 2028816 - VLAN IDs not released on failures
Summary: VLAN IDs not released on failures
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.10.0
Assignee: Michał Dulko
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-03 13:16 UTC by Michał Dulko
Modified: 2022-03-10 16:31 UTC (History)
0 users

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:31:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift kuryr-kubernetes pull 610 0 None open Bug 2028816: Fix VLAN ID management 2021-12-03 13:23:17 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:31:53 UTC

Description Michał Dulko 2021-12-03 13:16:58 UTC
Description of problem:
Kuryr doesn't release reserved VLAN IDs when there's an error on creating ports, resulting in exhausting the pool before it's really exhausted.

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

How reproducible:
I don't think you can reproduce this in normal circumstances.

Steps to Reproduce:
It can be done in a hacky way, I'm not 100% sure we want to invest in verification of this. This is however required if we're to stop restarting kuryr-controller on such failures as we do now.

Actual results:


Expected results:


Additional info:

Comment 6 errata-xmlrpc 2022-03-10 16:31:36 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056


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