Bug 2058674 - 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...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
Depends On: 2058673
Blocks: 2058675
TreeView+ depends on / blocked
Reported: 2022-02-25 15:19 UTC by Douglas Smith
Modified: 2022-07-19 07:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2058673
: 2058675 (view as bug list)
Last Closed: 2022-05-25 21:48:21 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1324 0 None Closed [BZ] latest RHEL 8.4 image (gen2) does not respond on initial first hard reboot ( restart operation) 2022-05-26 06:37:30 UTC
Red Hat Product Errata RHSA-2022:2272 0 None None None 2022-05-25 21:48:38 UTC

Description Douglas Smith 2022-02-25 15:19:55 UTC
+++ 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 3 Nikhil Simha 2022-04-26 19:00:05 UTC
Ran the following to verify this BZ:

oc get cronjob ip-reconciler -o yaml -n openshift-multus | grep -Pi "KUBERNETES_SERVICE_PORT|KUBERNETES_SERVICE_HOST|failedJobsHistoryLimit|backoffLimit|hostNetwork"
Got output:
failedJobsHistoryLimit: 1
      backoffLimit: 0
            - name: KUBERNETES_SERVICE_PORT
            - name: KUBERNETES_SERVICE_HOST
          hostNetwork: true

Marking this bug as verified.

Comment 6 errata-xmlrpc 2022-05-25 21:48:21 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 (Moderate: OpenShift Container Platform 4.8.41 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.


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