Bug 2079031 - Whereabouts ip-reconciler should be opt-in and not required
Summary: Whereabouts ip-reconciler should be opt-in and not required
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
Depends On: 2072215
Blocks: 2101915
TreeView+ depends on / blocked
Reported: 2022-04-26 17:53 UTC by Douglas Smith
Modified: 2022-06-28 19:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2072215
: 2101915 (view as bug list)
Last Closed: 2022-05-18 11:51:03 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1398 0 None open Bug 2079031: Make the use of the ip-reconciler cronjob opt-in by detecting IPAM type usage [backport 4.10] 2022-05-06 01:00:42 UTC
Red Hat Product Errata RHBA-2022:2178 0 None None None 2022-05-18 11:51:17 UTC

Description Douglas Smith 2022-04-26 17:53:04 UTC
+++ This bug was initially created as a clone of Bug #2072215 +++

Description of problem: The ip-reconciler used for Whereabouts can cause undue problems for those that don't implement Whereabouts. The reconciler should be opt-in and used only when Whereabouts is in use.

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

How reproducible: Easy to reproduce that the reconciler is required. Difficult to reproduce problems with the reconciler in a lab environment.

Steps to Reproduce:
1. Look for cronjobs in openshift-multus namespace.

Actual results: Cronjob is present.

Expected results: Cronjob is not present until a OpenShift networks object containing a RawCNIConfig with a "ipam" section which includes "type": "whereabouts" is present.

Comment 3 Weibin Liang 2022-05-10 13:12:40 UTC
Tested and verified in 4.10.0-0.nightly-2022-05-10-060208

[weliang@weliang ~]$ oc get nodes
NAME                                                        STATUS   ROLES    AGE   VERSION
weliang-5101-xsqfh-master-0.c.openshift-qe.internal         Ready    master   26m   v1.23.5+b463d71
weliang-5101-xsqfh-master-1.c.openshift-qe.internal         Ready    master   26m   v1.23.5+b463d71
weliang-5101-xsqfh-master-2.c.openshift-qe.internal         Ready    master   26m   v1.23.5+b463d71
weliang-5101-xsqfh-worker-a-vwbpk.c.openshift-qe.internal   Ready    worker   17m   v1.23.5+b463d71
weliang-5101-xsqfh-worker-b-9ns9s.c.openshift-qe.internal   Ready    worker   17m   v1.23.5+b463d71
weliang-5101-xsqfh-worker-c-cnqfp.c.openshift-qe.internal   Ready    worker   17m   v1.23.5+b463d71
[weliang@weliang ~]$ oc get cronjobs -n openshift-multus
No resources found in openshift-multus namespace.
[weliang@weliang ~]$ oc edit networks.operator.openshift.io cluster
network.operator.openshift.io/cluster edited
[weliang@weliang ~]$ watch -n2 oc get cronjobs -n openshift-multus
[weliang@weliang ~]$ oc edit networks.operator.openshift.io cluster
network.operator.openshift.io/cluster edited
[weliang@weliang ~]$ watch -n2 oc get cronjobs -n openshift-multus
[weliang@weliang ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2022-05-10-060208   True        False         8m23s   Cluster version is 4.10.0-0.nightly-2022-05-10-060208
[weliang@weliang ~]$

Comment 6 errata-xmlrpc 2022-05-18 11:51:03 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.14 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.