Bug 2034355 - The CNO should implement the Whereabouts IP reconciliation cron job
Summary: The CNO should implement the Whereabouts IP reconciliation cron job
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On: 2034352
Blocks: 2034358
TreeView+ depends on / blocked
 
Reported: 2021-12-20 18:50 UTC by Douglas Smith
Modified: 2022-02-16 11:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2034352
: 2034358 (view as bug list)
Environment:
Last Closed: 2022-02-16 11:19:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1266 0 None open Bug 2034355: Whereabouts IP Reconciliaton [backport 4.7] 2022-01-28 20:12:47 UTC
Red Hat Product Errata RHSA-2022:0492 0 None None None 2022-02-16 11:20:05 UTC

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


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