Bug 2034355

Summary: The CNO should implement the Whereabouts IP reconciliation cron job
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
Version: 4.10Keywords: FastFix
Target Milestone: ---   
Target Release: 4.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2034352
: 2034358 (view as bug list) Environment:
Last Closed: 2022-02-16 11:19:40 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: 2034352    
Bug Blocks: 2034358    

Description Douglas Smith 2021-12-20 18:50:27 UTC 
+++ This bug was initially created as a clone of Bug #2034352 +++

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

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

Description of problem: Without reconciliation whereabouts can leave IP addresses in a stranded state, the cluster-network-operator must implement the reconciliation cron job for whereabouts to address this.


How reproducible: (The cron job is not implemented)

Additional info: This will be backported all the way to 4.6.z and required companion changes, see also the whereabouts changes @ https://bugzilla.redhat.com/show_bug.cgi?id=2028963
Comment 1 Weibin Liang 2022-02-01 15:03:15 UTC 
Testing passed in cluster-bot: launch openshift/whereabouts-cni#79,openshift/cluster-network-operator#1266

[weliang@weliang Test]$ oc get clusterversion
NAME      VERSION                                                  AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.ci.test-2022-02-01-142111-ci-ln-zp1bifk-latest   True        False         10m     Cluster version is 4.7.0-0.ci.test-2022-02-01-142111-ci-ln-zp1bifk-latest
[weliang@weliang Test]$ 

[weliang@weliang Test]$ oc create -f ippool.yml -n openshift-multus
ippool.whereabouts.cni.cncf.io/192.168.2.224-28 created
[weliang@weliang Test]$ oc get ippools 192.168.2.224-28 -o yaml -n openshift-multus
apiVersion: whereabouts.cni.cncf.io/v1alpha1
kind: IPPool
metadata:
  creationTimestamp: "2022-02-01T15:00:02Z"
  generation: 2
  name: 192.168.2.224-28
  namespace: openshift-multus
  resourceVersion: "29743"
  selfLink: /apis/whereabouts.cni.cncf.io/v1alpha1/namespaces/openshift-multus/ippools/192.168.2.224-28
  uid: d1e1ff0d-dd7e-4872-b59f-b02da12af3fc
spec:
  allocations: {}
  range: 192.168.2.224/28
[weliang@weliang Test]$ oc create job --from=cronjob/ip-reconciler -n openshift-multus testrun-ip-reconciler
job.batch/testrun-ip-reconciler created
[weliang@weliang Test]$ oc get ippools 192.168.2.224-28 -o yaml -n openshift-multus
apiVersion: whereabouts.cni.cncf.io/v1alpha1
kind: IPPool
metadata:
  creationTimestamp: "2022-02-01T15:00:02Z"
  generation: 2
  name: 192.168.2.224-28
  namespace: openshift-multus
  resourceVersion: "29743"
  selfLink: /apis/whereabouts.cni.cncf.io/v1alpha1/namespaces/openshift-multus/ippools/192.168.2.224-28
  uid: d1e1ff0d-dd7e-4872-b59f-b02da12af3fc
spec:
  allocations: {}
  range: 192.168.2.224/28
[weliang@weliang Test]$
Comment 6 errata-xmlrpc 2022-02-16 11:19:40 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.7.43 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.

https://access.redhat.com/errata/RHSA-2022:0492