Created attachment 1585480 [details] versions keep refreshing with error message Description of problem: Cluster admin set some negative values for console.operator.openshift.io accessed from CRD Instance. Save the setting and try to update it back. It keeps reloading new version and can not get user update it. However oc command line can update it. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-06-27-204704 image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:47a0200aff7c9d4db5fb03d915220080939ebbce272b09c5c149bb6a774d7175 How reproducible: Always Steps to Reproduce: 1. Cluster admin goes to console.operator.openshift.io detail page accessed from CRD Instance. (url: k8s/cluster/operator.openshift.io~v1~Console/cluster/yaml) 2. Try to set customization some invalid value: customization: brand: ocp customLogoFile: key: invalid name: myconfig-ngtv customProductName: my-custom-name 3. Save and check 4. Try to set it back. Actual results: 3. After save, it pops up the error message "his object has been updated. Click reload to see the new version." 4. It keeps refreshing newer version, user can not set it back unless use "oc edit console.operator.openshift.io". Refer to the screenshot. Expected results: 4. Should stop keeps refreshing newer versions. Additional info: 1) This could be correctly set: customization: brand: ocp customProductName: my-custom-name 2) CLI works using "oc edit console.operator.openshift.io"
Sounds like the operator is hot looping on bad config
Fixing PR: https://github.com/openshift/console-operator/pull/253
Thanks Jakub! Tested on 4.2.0-0.nightly-2019-08-18-054211. There is no loop refreshing for versions now. However the invalid value won't show any error message and it could be saved "successfully". So is there any plan to fix for the error message?
So the message should be shown but you need to bump logging for the console-operator. Otherwise just the 'CustomLogoConfigMapDegraded' condition will be shown: ---- - lastTransitionTime: '2019-08-20T09:37:18Z' message: custom logo file myconfig-ngtv not found reason: CustomLogoConfigMapError status: 'True' type: CustomLogoConfigMapDegraded ----
The message is correct since the config itself was in fact saved successfully. As long as the console is correctly reporting degraded when the config map key doesn't exist, this is working as intended.
Thanks for the confirm. This could be Verified.
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-2019:2922