Bug 2034351 - 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.9.z
Assignee: Douglas Smith
QA Contact: Weibin Liang
URL:
Whiteboard:
Depends On: 2034350
Blocks: 2034352
TreeView+ depends on / blocked
 
Reported: 2021-12-20 18:45 UTC by Douglas Smith
Modified: 2022-01-31 18:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2034350
: 2034352 (view as bug list)
Environment:
Last Closed: 2022-01-31 18:22:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1264 0 None open Bug 2034351: Whereabouts IP Reconciliaton [backport 4.9] 2022-01-06 18:23:06 UTC
Red Hat Product Errata RHBA-2022:0279 0 None None None 2022-01-31 18:22:54 UTC

Description Douglas Smith 2021-12-20 18:45:26 UTC
+++ 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-01-18 21:00:08 UTC
Using cluster-bot build the cluster with fixing PR: launch openshift/cluster-network-operator#1264 aws
But verifying testing failed:

[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-01-18T15:36:01Z"
  generation: 1
  managedFields:
  - apiVersion: whereabouts.cni.cncf.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:allocations:
          .: {}
          f:1:
            .: {}
            f:id: {}
            f:podref: {}
        f:range: {}
    manager: kubectl-create
    operation: Update
    time: "2022-01-18T15:36:01Z"
  name: 192.168.2.224-28
  namespace: openshift-multus
  resourceVersion: "28001"
  uid: 3c9d7d46-65bb-45f0-a686-c799571c1b65
spec:
  allocations:
    "1":
      id: f7559e44472d139ce9333d7f6094c81866eb65a0d62cce5576a8b89990011cd9
      podref: default/wbsamplepod
  range: 192.168.2.224/28
[weliang@weliang Test]$ oc create job --from=cronjob/ip-reconciler -n openshift-multus testrun-ip-reconciler
error: from must be an existing cronjob: no kind "CronJob" is registered for version "batch/v1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
[weliang@weliang Test]$ oc create job --from=cronjobs/ip-reconciler -n openshift-multus testrun-ip-reconciler
error: from must be an existing cronjob: no kind "CronJob" is registered for version "batch/v1" in scheme "k8s.io/kubectl/pkg/scheme/scheme.go:28"
[weliang@weliang Test]$ oc get job ip-reconciler -oyaml
Error from server (NotFound): jobs.batch "ip-reconciler" not found
[weliang@weliang Test]$ oc get clusterversion
NAME      VERSION                                                  AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.ci.test-2022-01-18-144817-ci-ln-fgwck8b-latest   True        False         21m     Cluster version is 4.9.0-0.ci.test-2022-01-18-144817-ci-ln-fgwck8b-latest
[weliang@weliang Test]$

Comment 6 errata-xmlrpc 2022-01-31 18:22:33 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.9.18 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.

https://access.redhat.com/errata/RHBA-2022:0279


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