Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1748182

Summary: New console pod failed to be Running when logo set to PNG
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED DUPLICATE QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman
Target Milestone: ---   
Target Release: ---   
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: 2019-09-03 09:50:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description XiaochuanWang 2019-09-03 06:14:45 UTC
Description of problem:
When set the logo with PNG format, the new console pod becomes CrashLoopBackOff

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. redeploy should be triggered, check the openshift-console pod which is crash. Check the Configmap cmpng Binary Data which is correct.

Actual results:
New pod becomes CrashLoopBackOff

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:
Pods should be Running

Additional info:

Comment 1 XiaochuanWang 2019-09-03 09:50:00 UTC
Closing this issue for finding the actual problem: https://bugzilla.redhat.com/show_bug.cgi?id=1748280

*** This bug has been marked as a duplicate of bug 1748280 ***