Bug 2058677

Summary:	whereabouts IPAM CNI ip-reconciler cronjob specification requires hostnetwork, api-int lb usage & proper backoff
Product:	OpenShift Container Platform	Reporter:	Douglas Smith <dosmith>
Component:	Networking	Assignee:	Douglas Smith <dosmith>
Networking sub component:	multus	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	high
Priority:	high	CC:	weliang
Version:	4.10
Target Milestone:	---
Target Release:	4.6.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2058675	Environment:
Last Closed:	2022-08-24 19:49:58 UTC	Type:	---
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:	2058675
Bug Blocks:

Description Douglas Smith 2022-02-25 15:22:08 UTC

+++ This bug was initially created as a clone of Bug #2058675 +++

+++ This bug was initially created as a clone of Bug #2058674 +++

+++ This bug was initially created as a clone of Bug #2058673 +++

+++ This bug was initially created as a clone of Bug #2058672 +++

+++ This bug was initially created as a clone of Bug #2058671 +++

Description of problem: A number of changes related to the ip-reconciler ( need to be properly implemented, these include:

Impact: Without the proper backoff and replacement policies, many failed jobs can build up. Additionally without hostnetworking and use of the api-int lb network connectivity problems which cause errors.

Note: A set of changes to the ip-reconciler itself

Fixes to include in this (and subsequent backports) include:

* auto clean failed jobs (https://github.com/openshift/cluster-network-operator/pull/1318)
* Use host network and api-int (https://github.com/openshift/cluster-network-operator/pull/1302)
* Disable retries on failure (https://github.com/openshift/cluster-network-operator/pull/1290)

Comment 1 Scott Dodson 2022-08-24 19:49:58 UTC

The only open case attached to the chain of bugs back to 4.11 is against 4.8. It does not appear that anyone is awaiting fixes for this in 4.6.