Bug 2041940 - Namespace pre-population not happening till a Pod is created
Summary: Namespace pre-population not happening till a Pod is created
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.11.0
Assignee: Maysa Macedo
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-18 15:05 UTC by Maysa Macedo
Modified: 2022-08-10 10:43 UTC (History)
2 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift api pull 1132 0 None open BUg 2041940: Fix enablePortPoolsPrepopulation setting definition 2022-03-10 10:05:46 UTC
Github openshift openshift-docs pull 42046 0 None open Bug 2041940: Fix enablePortPoolsPrepopulation setting definition 2022-02-17 11:08:55 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:43:25 UTC

Description Maysa Macedo 2022-01-18 15:05:28 UTC 
Description of problem:

The new method included in 4.10 of providing the Network to the OCP Namespaces only when a Pod not in host network is created in that Namespace, breaks the pre-population feature since the Namespace won't be pre-populated with any Neutron Ports till a Pod gets created.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 errata-xmlrpc 2022-08-10 10:43:03 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069
Note You need to log in before you can comment on or make changes to this bug.