Bug 1750790
Summary: | Custom logo volume mounts not set on the deployment when setting custom logo | ||
---|---|---|---|
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, yapei |
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:40:52 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
Jakub Hadvig
2019-09-10 13:31:15 UTC
$ oc create configmap custom-pic --from-file=mypic.png -n openshift-config configmap/custom-pic created $ oc get console.operator.openshift.io cluster -o json | jq '.spec.customization' { "brand": "azure", "customLogoFile": { "key": "mypic.png", "name": "custom-pic" }, "customProductName": "my-custom-name" } $ oc get pods -n openshift-console NAME READY STATUS RESTARTS AGE console-56d5fddb99-2cz8w 0/1 ContainerCreating 0 1s console-56d5fddb99-pt8h9 1/1 Running 0 14s console-77664894d-chqqp 0/1 Terminating 0 88m console-77664894d-cjhd6 1/1 Running 1 92m downloads-5cdcbb69d4-fv5gg 1/1 Running 0 93m downloads-5cdcbb69d4-qmrff 1/1 Running 0 93m $ oc get pods -n openshift-console NAME READY STATUS RESTARTS AGE console-56d5fddb99-2cz8w 1/1 Running 0 40s console-56d5fddb99-pt8h9 1/1 Running 0 53s downloads-5cdcbb69d4-fv5gg 1/1 Running 0 94m downloads-5cdcbb69d4-qmrff 1/1 Running 0 94m console pods can be started and running successfully Verified on 4.2.0-0.nightly-2019-09-11-202233 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 |