Bug 2085510

Summary:	Reserved port 9104 prevents a roll out of new cluster-network-operator Pod during SNO 4.10 upgrade
Product:	OpenShift Container Platform	Reporter:	Patryk Matuszak <pmatusza>
Component:	Networking	Assignee:	Patryk Matuszak <pmatusza>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high
Version:	4.10
Target Milestone:	---
Target Release:	4.10.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-07 13:24:32 UTC	Type:	Bug
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:	2085530
Bug Blocks:	2101092

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:
1.
2.
3.

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.

https://access.redhat.com/errata/RHBA-2022:4882