Bug 1746925 - Custom logo file cant be found when SVG
Summary: Custom logo file cant be found when SVG
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-29 14:14 UTC by Jakub Hadvig
Modified: 2019-10-16 06:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:38:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console-operator pull 280 0 None None None 2019-08-30 11:57:36 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:38:41 UTC

Description Jakub Hadvig 2019-08-29 14:14:13 UTC 
Description of problem:
When creating a SVG type custom logo, the created configMap will contain the data in the data field not in the binaryData as in case of PNG, JPG,.. which will cause the console pod to CrashLoop.


Version-Release number of selected component (if applicable):
4.2.0-0.ci-2019-08-28-103038

How reproducible:
Always


Steps to Reproduce:
1. oc create configmap custom-logo-svg --from-file=logo.svg -n openshift-config
2. edit Console operator.openshift.io for customization
spec:
  customization:
    brand: azure
    customLogoFile:
      key: logo.svg
      name: custom-logo-svg
    customProductName: my-custom-name
3. redeploy should be triggered

Actual results:
Redeployed pods will CrashLoop

Expected results:
Redeployed pods should be using the custom logo in the SVG format

Additional info:
Comment 1 Jakub Hadvig 2019-08-30 10:06:28 UTC 
https://github.com/openshift/console-operator/pull/280
Comment 3 XiaochuanWang 2019-09-03 06:15:39 UTC 
SVG logo could be correctly displayed.
Verified on 4.2.0-0.nightly-2019-09-02-172410
Comment 4 errata-xmlrpc 2019-10-16 06:38:33 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-2019:2922
Note You need to log in before you can comment on or make changes to this bug.