Bug 1855567

Summary:	console-operator is updating config.openshift.io objects for no apparent reason
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Management Console	Assignee:	Jakub Hadvig <jhadvig>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.6	CC:	aos-bugs, jokerman, sdodson, spadgett, wking, yanpzhan
Target Milestone:	---
Target Release:	4.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-22 12:20:42 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:	1853270
Bug Blocks:

Description OpenShift BugZilla Robot 2020-07-10 08:36:17 UTC

+++ This bug was initially created as a clone of Bug #1853270 +++

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

--- Additional comment from jhadvig on 2020-07-10 08:07:22 UTC ---

Waiting for bug to get verified. Adding UpcomingSprint to have it reevaluated in the next cycle.

Comment 3 Yanping Zhang 2020-07-17 03:38:51 UTC

Checked on 4.6 cluster with payload 4.6.0-0.nightly-2020-07-16-162619.
1.Go to Administration -> Cluster Settings
2.Click on Global Configuration -> Console
3. Switch to Yaml view, and wait for a couple of seconds, if no changes to configuration, will not show "This object has been updated" message.
The bug is fixed.

Comment 4 Yanping Zhang 2020-07-17 04:05:17 UTC

Sorry, cluster info in Comment 3 is not correct, the bug is verified on 4.5 cluster with payload 4.5.0-0.nightly-2020-07-16-193418.

Comment 6 errata-xmlrpc 2020-07-22 12:20:42 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.

https://access.redhat.com/errata/RHBA-2020:2956