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

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2034351
: 2034355 (view as bug list)
Last Closed: 2022-02-16 06:51:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1265 0 None open Bug 2034352: Whereabouts IP Reconciliaton [backport 4.8] 2022-01-25 21:11:21 UTC
Red Hat Product Errata RHBA-2022:0484 0 None None None 2022-02-16 06:51:59 UTC

Description Douglas Smith 2021-12-20 18:47:13 UTC
+++ 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-01-26 14:58:15 UTC
Testing passed in cluster-bot: launch openshift/cluster-network-operator#1265

Comment 6 errata-xmlrpc 2022-02-16 06:51: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 (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.


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