Description of problem: When setting custom logo the volume mounts are not set on the deployment, causing pod to CrashLoop Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. oc create configmap custom-pic --from-file=pic.png -n openshift-config 2. edit Console operator.openshift.io for customization spec: customization: brand: azure customLogoFile: key: pic.png name: custom-pic customProductName: my-custom-name 3. redeploy should be triggered Actual results: Redeployed pods will CrashLoop Expected results: Redeployed pods won't CrashLoop Additional info:
$ 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