Description of problem: Config console for a logo, when all console pods running, update the console config for new logo, then the new triggered console pod will crash in loop. Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-09-02-172410 How reproducible: Always Steps to Reproduce: 1. oc create configmap cmpng --from-file=logo.png -n openshift-config 2. edit console.operator.openshift.io for customization spec: customization: brand: azure customLogoFile: key: logo.png name: cmpng customProductName: my-custom-name 3. When the pods are running, repeat step 1 and 2 (create new configmap and update console.operator.openshift.io). Check the new triggered pod. Actual results: New triggered pod will be CrashLoopBackOff from Error. Picture is saved to Binary Data in configmap $ oc logs -f console-795d749f7c-l87kb -n openshift-console 2019/09/3 06:07:03 cmd/main: could not read logo file: stat /var/logo/logo.png: no such file or directory Expected results: All pods should be Running. Additional info:
*** Bug 1748182 has been marked as a duplicate of this bug. ***
Bug is not reproducible with images that are saved in the confgiMap's `data` field, eg. svg format The issue was traced down to the library-go where the sync is not couting with the `binaryData` field
Customized the logo twice and this is not reproduced. Verified on 4.2.0-0.nightly-2019-09-08-180038
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