Logging-view container issues - Missing files about logging-view-plugin HOT 6 CLOSED

Hi,

Has anyone had a chance to look at the above issue of missing files @ndelrey raised.

Hi there

On Dec I was able to deploy Loki in an OCP 4.10 (s390x arch) and enabling the logging-view console without problems Logging operator was 5.4.3. Something happened during the X-mas holidays (not sure if someone upgraded the operator manually or it was due automatically) but the. logging-view plugin is not longer running (now it is running 5.5)

I can see logs like the following

{"_ts":"2023-01-18T11:39:02.792504266Z","_level":"0","_component":"cluster-logging-operator","_message":"reconciling console","_error":{"msg":"ConsolePlugin.console.openshift.io \"logging-view-plugin\" is invalid: spec.proxy.service.name: Invalid value: \"\": spec.proxy.service.name in body should be at least 1 chars long"},"plugin":"console.openshift.io/v1alpha1/consoleplugins/logging-view-plugin"}

and

2023/01/18 12:09:04 [error] 7#0: *2 open() "/usr/share/nginx/html/locales/en/plugin_logging-view-plugin.json" failed (2: No such file or directory), client: 10.129.0.96, server: , request: "GET /locales/en/plugin_logging-view-plugin.json HTTP/1.1", host: "logging-view-plugin.openshift-logging.svc.cluster.local:9443", referrer: "https://console-openshift-console.apps.[redacted]/k8s/ns/openshift-logging/clusterserviceversions/cluster-logging.5.5.5/logging.openshift.io~v1~ClusterLogging/instance/yaml"

It seems there are some missing files in the container and OCP Console can't connect with the service and it is not shown in the console

I've tried to downgrade completely the stack (back to 5.4.9), and I can see the same thing

For some reason the plugin_logging-view-plugin.json is not in the docker image. Indeed there is no /usr/share/nginx/html/locales folder

Is anyone aware of that?

Thanks in advance

from logging-view-plugin.

@ndelrey @abdinoorabdi tnhx for reporting the issue. It seems we have 2 different issues here.

{"_ts":"2023-01-18T11:39:02.792504266Z","_level":"0","_component":"cluster-logging-operator","_message":"reconciling console","_error":{"msg":"ConsolePlugin.console.openshift.io \"logging-view-plugin\" is invalid: spec.proxy.service.name: Invalid value: \"\": spec.proxy.service.name in body should be at least 1 chars long"},"plugin":"console.openshift.io/v1alpha1/consoleplugins/logging-view-plugin"}

It appears that the plugin configuration has an invalid name for the proxy service. Can you try disabling the plugin and re enabling it again so it can be correctly reconciled. We had a regression issue for 4.10 and 5.5 that was fixed.

2023/01/18 12:09:04 [error] 7#0: *2 open() "/usr/share/nginx/html/locales/en/plugin_logging-view-plugin.json" failed (2: No such file or directory), client: 10.129.0.96, server: , request: "GET /locales/en/plugin_logging-view-plugin.json HTTP/1.1", host: "logging-view-plugin.openshift-logging.svc.cluster.local:9443", referrer: "https://console-openshift-console.apps.[redacted]/k8s/ns/openshift-logging/clusterserviceversions/cluster-logging.5.5.5/logging.openshift.io~v1~ClusterLogging/instance/yaml"

Refers to translation files that are not added yet but should fallback to the default language (english), this feature is planned for 5.7

from logging-view-plugin.

Hey @jgbernalp , thanks for your help

Yes, I've tried to enable/disable the plugin several times and no way

Related to the translation files... for some reason the service is not doing this "fallback" or at least it tries to load some files from /locales/en ... and they are not longer there.

I guess that something gone from this last regression issue

Do you know when it is planned the new release?

from logging-view-plugin.

@jgbernalp
any news on this issue?
Is it fixed on Cluster-Logging-Operator 5.6?

from logging-view-plugin.

@ndelrey The PR adding the translations was added #84 and planned to land in 5.7.

OCP 4.10 tries to load the translation files even if the plugin doesn't support it. This is a known issue that was addressed in 4.11

from logging-view-plugin.

Thanks a lot for the feedback @jgbernalp
@abdinoorabdi upgrading may solve the issue

from logging-view-plugin.