-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
During an upgrade to an OpenShift 4.19.7+ version with an invalid logging-view-plugin ConsolePlugin, the console pods will end up crash looping and the upgrade may not complete. oc get pods -n openshift-console -l component=ui NAME READY STATUS RESTARTS AGE console-5bf56fd8ff-qxfwn 0/1 CrashLoopBackOff 303 (4m20s ago) 25h console-5bf56fd8ff-sv46m 0/1 CrashLoopBackOff 302 (70s ago) 25h console-856988748c-zn7cw 1/1 Running 0 26h The following errors are seen in the console-operator pod. oc logs console-operator-78445c68b5-jgkbn -n openshift-console-operator E1110 05:44:09.300350 1 configmap.go:189] unknown backend type for "logging-view-plugin" plugin: "". Currently only "Service" backend type is supported. E1110 05:44:09.300377 1 configmap.go:210] unknown proxy service type for "logging-view-plugin" plugin: "". Currently only "Service" proxy endpoint type is supported.
Version-Release number of selected component (if applicable):
OpenShift Container Platform 4.19, and I believe it will be 4.19.7+.
How reproducible:
I am able to reproduce this issue.
Steps to Reproduce:
Steps included in comment below.
Actual results:
The console pod is crashing and the errors are seen in the console operator pod.
Expected results:
The console pod doesn't crash and no errors are seen in the console operator pod.
Additional info:
- duplicates
-
OCPBUGS-60782 Enabling invalid or missing plugin causes console to crash loop
-
- Verified
-