Bug 1746925
| Summary: | Custom logo file cant be found when SVG | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jakub Hadvig <jhadvig> |
| Component: | Management Console | Assignee: | Jakub Hadvig <jhadvig> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.0 | CC: | aos-bugs, jokerman, spadgett, xiaocwan |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| 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-10-16 06:38:33 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: | |||
SVG logo could be correctly displayed. Verified on 4.2.0-0.nightly-2019-09-02-172410 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 |
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: