Bug 2034351

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.9.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2034350
: 2034352 (view as bug list) Environment:
Last Closed: 2022-01-31 18:22:33 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: 2034350    
Bug Blocks: 2034352    

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/ created
[weliang@weliang Test]$ oc get ippools -o yaml -n openshift-multus
apiVersion: whereabouts.cni.cncf.io/v1alpha1
kind: IPPool
  creationTimestamp: "2022-01-18T15:36:01Z"
  generation: 1
  - apiVersion: whereabouts.cni.cncf.io/v1alpha1
    fieldsType: FieldsV1
        .: {}
          .: {}
            .: {}
            f:id: {}
            f:podref: {}
        f:range: {}
    manager: kubectl-create
    operation: Update
    time: "2022-01-18T15:36:01Z"
  namespace: openshift-multus
  resourceVersion: "28001"
  uid: 3c9d7d46-65bb-45f0-a686-c799571c1b65
      id: f7559e44472d139ce9333d7f6094c81866eb65a0d62cce5576a8b89990011cd9
      podref: default/wbsamplepod
[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.