Bug 2058677 - whereabouts IPAM CNI ip-reconciler cronjob specification requires hostnetwork, api-int lb usage & proper backoff
Summary: whereabouts IPAM CNI ip-reconciler cronjob specification requires hostnetwork...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.6.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On: 2058675
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 15:22 UTC by Douglas Smith
Modified: 2022-08-24 19:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2058675
Environment:
Last Closed: 2022-08-24 19:49:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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