Bug 2028966
Summary: | Whereabouts should reconcile stranded IP addresses | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Douglas Smith <dosmith> | |
Component: | Networking | Assignee: | 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.10 | Keywords: | FastFix | |
Target Milestone: | --- | |||
Target Release: | 4.8.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: |
Feature: Implements an IP reconciliation job for Whereabouts IPAM CNI called "ip-reconciler" which runs as a Kubernetes cronjob.
Reason: On occasion events occur where the CNI DEL action will not complete for a given pod (for example, a forcefully powered off node), and in such a case stored IP address allocations may be left stranded and unable to be allocated without manual intervention.
Result: Stranded IP address allocations are garbage collected automatically on a periodic basis to free unused IP addresses.
|
Story Points: | --- | |
Clone Of: | 2028964 | |||
: | 2028967 (view as bug list) | Environment: | ||
Last Closed: | 2022-02-16 06:51: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: | 2028964 | |||
Bug Blocks: | 2028967 |
Description
Douglas Smith
2021-12-03 20:27:18 UTC
@dosmith Use cluster-bot to create testing PR#78 cluster: launch https://github.com/openshift/whereabouts-cni/pull/78 But got nothing when oc get cronjobs -n openshift-multus [weliang@weliang ~]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.ci.test-2022-01-25-212450-ci-ln-d20n1p2-latest True False 8m27s Cluster version is 4.8.0-0.ci.test-2022-01-25-212450-ci-ln-d20n1p2-latest [weliang@weliang ~]$ oc get cronjobs -n openshift-multus No resources found in openshift-multus namespace. [weliang@weliang ~]$ oc version Client Version: 4.8.0-0.nightly-2022-01-24-131630 Server Version: 4.8.0-0.ci.test-2022-01-25-212450-ci-ln-d20n1p2-latest Kubernetes Version: v1.21.2-1639+bb8d50ab72040c-dirty Tested and verified in 4.8.0-0.nightly-2022-01-27-134250 [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-27T21:09:42Z" generation: 1 name: 192.168.2.224-28 namespace: openshift-multus resourceVersion: "37863" uid: 3a5dbb15-1c27-4ee6-9ad6-e629e6d128e2 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 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-01-27T21:09:42Z" generation: 2 name: 192.168.2.224-28 namespace: openshift-multus resourceVersion: "38032" uid: 3a5dbb15-1c27-4ee6-9ad6-e629e6d128e2 spec: allocations: {} range: 192.168.2.224/28 [weliang@weliang Test]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2022-01-27-134250 True False 7m16s Cluster version is 4.8.0-0.nightly-2022-01-27-134250 [weliang@weliang Test]$ 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.8.31 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:0484 |