Bug 2079031

Summary: Whereabouts ip-reconciler should be opt-in and not required
Product: OpenShift Container Platform Reporter: Douglas Smith <dosmith>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: weliang, wking
Version: 4.11   
Target Milestone: ---   
Target Release: 4.10.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2072215
: 2101915 (view as bug list) Environment:
Last Closed: 2022-05-18 11:51:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 2072215    
Bug Blocks: 2101915    

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.