Bug 1892320 - cluster-etcd-operator flooding the logs in steady state
Summary: cluster-etcd-operator flooding the logs in steady state
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Suresh Kolichala
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks: 1899563
TreeView+ depends on / blocked
 
Reported: 2020-10-28 13:39 UTC by Suresh Kolichala
Modified: 2020-11-30 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1899563 (view as bug list)
Environment:
Last Closed: 2020-11-30 16:45:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 381 0 None closed remove etcdMemberIPMigrator controller 2020-12-08 05:53:30 UTC
Red Hat Product Errata RHBA-2020:5115 0 None None None 2020-11-30 16:45:53 UTC

Description Suresh Kolichala 2020-10-28 13:39:21 UTC
Description of problem:
In steady state, the logs are flooded with messages rolling 600 logs per minute.

Most of the messages appear unremarkable and can be cut down.

See the issue reported here:
https://github.com/openshift/cluster-etcd-operator/issues/466

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


How reproducible:


Steps to Reproduce:
1. Install a 4.5 cluster.
2. In steady state, observe cluster-etcd-operator logs.

Actual results:
Log flood of uneventful events.

Expected results:
There should be minimal logging, if no remarkable events are happening.

Additional info:

Comment 8 errata-xmlrpc 2020-11-30 16:45:31 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.6.6 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-2020:5115


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