Bug 1853270 - console-operator is updating config.openshift.io objects for no apparent reason
Summary: console-operator is updating config.openshift.io objects for no apparent reason
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
Depends On:
Blocks: 1855567
TreeView+ depends on / blocked
Reported: 2020-07-02 10:14 UTC by Vadim Rutkovsky
Modified: 2020-10-27 16:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-27 16:11:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console-operator pull 445 0 None closed Bug 1853270: Update console config on change 2020-07-13 06:17:25 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:12:07 UTC

Description Vadim Rutkovsky 2020-07-02 10:14:03 UTC
Cluster console object is being updated every second, although 

Steps To Reproduce:
1. Administration -> Cluster Settings
2. Global Configuration -> Console
3. Switch to Yaml view

After a couple of seconds "This object has been updated" message would appear. revisionVersion is bumped although no changes to configuration have been made.

This makes unnecessary load on apiserver and etcd

Comment 1 Jakub Hadvig 2020-07-10 08:07:22 UTC
Waiting for bug to get verified. Adding UpcomingSprint to have it reevaluated in the next cycle.

Comment 5 XiaochuanWang 2020-07-13 06:42:23 UTC
Follow the description steps, this does not reproduce again.
Verified on 4.6.0-0.nightly-2020-07-12-204440

Comment 7 errata-xmlrpc 2020-10-27 16:11:47 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 GA Images), 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.