-
Bug
-
Resolution: Done
-
Major
-
Logging 5.8.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
-
-
Log Collection - Sprint 239
Description: logging-view-plugin deployment/resources are not created after console plugin is enabled
Console logs before plugin is enabled.
$ oc logs -f console-7448c464d8-d2cnm -n openshift-console W0616 18:10:54.869091 1 main.go:229] Flag inactivity-timeout is set to less then 300 seconds and will be ignored! I0616 18:10:54.869126 1 main.go:359] cookies are secure! I0616 18:10:54.901785 1 main.go:831] Binding to [::]:8443... I0616 18:10:54.901816 1 main.go:833] using TLS I0616 18:10:57.902272 1 metrics.go:141] serverconfig.Metrics: Update ConsolePlugin metrics... I0616 18:10:57.916166 1 metrics.go:151] serverconfig.Metrics: Update ConsolePlugin metrics: &map[redhat:map[disabled:1]] (took 13.662661ms) I0616 18:10:59.902473 1 metrics.go:88] usage.Metrics: Count console users... I0616 18:11:00.407444 1 metrics.go:174] usage.Metrics: Update console users metrics: 1 kubeadmin, 0 cluster-admins, 0 developers, 0 unknown/errors (took 504.949161ms) E0616 18:11:01.027936 1 handlers.go:141] failed to get endpoint for "logging-view-plugin" plugin E0616 18:11:12.275313 1 handlers.go:141] failed to get endpoint for "logging-view-plugin" plugin E0616 18:11:16.082397 1 handlers.go:141] failed to get endpoint for "logging-view-plugin" plugin E0616 18:11:27.340547 1 handlers.go:141] failed to get endpoint for "logging-view-plugin" plugin E0616 18:11:31.216312 1 handlers.go:141] failed to get endpoint for "logging-view-plugin" plugin
console logs after plugin is enabled
$ oc logs -f console-57cdf4d4f-42hvc -n openshift-console W0616 18:10:17.644506 1 main.go:229] Flag inactivity-timeout is set to less then 300 seconds and will be ignored! I0616 18:10:17.644520 1 main.go:239] The following console plugins are enabled: I0616 18:10:17.644527 1 main.go:241] - logging-view-plugin I0616 18:10:17.644551 1 main.go:359] cookies are secure! I0616 18:10:17.680123 1 server.go:628] The following console endpoints are now proxied to these services: I0616 18:10:17.680152 1 server.go:631] - /api/proxy/plugin/logging-view-plugin/backend/ -> https://lokistack-dev-gateway-http.openshift-logging.svc.cluster.local:8080 I0616 18:10:17.680282 1 main.go:831] Binding to [::]:8443... I0616 18:10:17.680310 1 main.go:833] using TLS I0616 18:10:20.680526 1 metrics.go:141] serverconfig.Metrics: Update ConsolePlugin metrics... I0616 18:10:20.693952 1 metrics.go:151] serverconfig.Metrics: Update ConsolePlugin metrics: &map[redhat:map[enabled:1]] (took 13.405888ms) I0616 18:10:22.680809 1 metrics.go:88] usage.Metrics: Count console users... I0616 18:10:23.187388 1 metrics.go:174] usage.Metrics: Update console users metrics: 1 kubeadmin, 0 cluster-admins, 0 developers, 0 unknown/errors (took 506.549136ms) E0616 18:10:25.978897 1 handlers.go:164] GET request for "logging-view-plugin" plugin failed: Get "https://logging-view-plugin.openshift-logging.svc.cluster.local:9443/plugin-manifest.json": dial tcp: lookup logging-view-plugin.openshift-logging.svc.cluster.local: no such host 2023/06/16 18:10:25 http: panic serving 10.131.0.7:35946: runtime error: invalid memory address or nil pointer dereference goroutine 172 [running]: net/http.(*conn).serve.func1() /usr/lib/golang/src/net/http/server.go:1850 +0xbf panic({0x2ffb360, 0x4c98090}) /usr/lib/golang/src/runtime/panic.go:890 +0x262 .....
logging_console_plugin image: registry.redhat.io/openshift-logging/logging-view-plugin-rhel9@sha256:630e3b04b83c7f712941bbf08639bbbf14027e3510fb1b0e3c593f3584648c86
Version:
$ oc get csv -n openshift-logging
NAME DISPLAY VERSION REPLACES PHASE
cluster-logging.v5.8.0 Red Hat OpenShift Logging 5.8.0 Succeeded
loki-operator.v5.8.0 Loki Operator 5.8.0 Succeeded
Steps to reproduce:
1) Deploy CLO and Loki Operators.
2) Forward logs to default logStore loki
3) Check console logs before enabling plugin
4) Check console logs after enabling plugin
Actual Result:
logging-view-plugin deployment/resources are not created. Errors on console pods.
Expected Result:
logging-view-plugin deployment/resources should be created after plugin is enabled without errors.
How reproducible: Always
- links to
- mentioned on
