Bug 2085510 - Reserved port 9104 prevents a roll out of new cluster-network-operator Pod during SNO 4.10 upgrade
Summary: Reserved port 9104 prevents a roll out of new cluster-network-operator Pod du...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Patryk Matuszak
QA Contact: zhaozhanqi
Depends On: 2085530
Blocks: 2101092
TreeView+ depends on / blocked
Reported: 2022-05-13 14:49 UTC by Patryk Matuszak
Modified: 2022-06-25 12:07 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-06-07 13:24:32 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1445 0 None open [release-4.10] Bug 2085510: OCPVE-106 Customize rollout strategy to fix SNO upgrade 2022-05-13 15:30:12 UTC
Red Hat Product Errata RHBA-2022:4882 0 None None None 2022-06-07 13:24:46 UTC

Description Patryk Matuszak 2022-05-13 14:49:59 UTC
Description of problem:

Due to CNO Pod having a 9104 port reservation, a new Pod cannot be scheduled on the same node. That causes a deployment to not progress and upgrade fail at around 80%.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 zhaozhanqi 2022-05-31 03:11:28 UTC
Move this to verified.

Comment 6 errata-xmlrpc 2022-06-07 13:24:32 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 (OpenShift Container Platform 4.10.17 bug fix 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.


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