Bug 1832901

Summary: etcd-operator spuriously reconciles in response to global configmap watch events
Product: OpenShift Container Platform Reporter: Dan Mace <dmace>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: sbatsche, skolicha, wking
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1832919 (view as bug list) Environment:
Last Closed: 2020-07-13 17:35:55 UTC Type: Bug
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:    
Bug Blocks: 1832919    

Description Dan Mace 2020-05-07 12:59:16 UTC
Description of problem:

The etcd-operator is unnecessarily triggering reconciliation in response to any configmap watch event across all namespaces. Given the volume and churn of configmaps in any nontrivial production cluster, combined with the actions performed during a reconciliation (which at present include active etcd API calls to list members and their status), the resulting chatter with etcd seems excessive (although I haven't yet performed systematic measurements).

Version-Release number of selected component (if applicable):

4.4, 4.5

How reproducible:

Launch a new cluster IPI cluster on any platform.

Actual results:

The etcd-operator reconciles once for every configmap in the system, and then in response to any change to any configmap in the system after the initial sync.

Expected results:

The etcd-operator should only reconcile when relevant changes (e.g. node churn) occur.

Additional info:

Comment 3 ge liu 2020-05-20 07:26:22 UTC
Tried with 4.5.0-0.nightly-2020-05-19-041951, the map trend looks like well, pls comments if any misunderstanding.

Comment 5 Sam Batschelet 2020-05-21 18:07:23 UTC
*** Bug 1812718 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2020-07-13 17:35:55 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.