-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
After updating their development cluster from 4.16 to 4.17.20, customer is experiencing some issues with the UI not loading.
Version-Release number of selected component (if applicable):
4.17
How reproducible:
UnKnown
Steps to Reproduce:
Unknown
Actual results:
1. When attempting to create a Route in the UI in a project that does not have any other routes, the UI just hangs. If they do the same in a project that has existing routes, it works fine. This issue occurs both with their cluster-admin user and other users with lower-level access (such as project edit) 2. When attempting to browse to the Observe view from a Pod metric, the UI hangs for some of their users. Multiple users experience this problem, using different browsers. They are not seeing these problems in their Production cluster, which is still on 4.16. Regarding the UI issue with the Routes, they've found that the issue seems to only occur when in the Developer view, not the Administrator view. 3. Also, the URL path is different depending on whether the route is created from the dev view (/routes/new/form) or the admin view (/route.openshift.iov1Route/new/form) In their Production cluster running 4.16, the same path is used in both the Dev and the Admin view. (/routes/~new/form) They've now also been able to reproduce the issue with the Observe > Metrics view. It is also related to which view the user is in (Developer or Administrator). A few things I have noticed that might be an indication of UI Issues: 1. There is a logging plugin for the observability operator deployed, as described here: https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/cluster_observability_operator/observability-ui-plugins#coo-logging-ui-plugin-install_logging-ui-plugin. They have this plugin in both their Dev and Prod clusters, and are not seeing the same issues in prod. 2. Also, we spent a significant amount of time checking the must-gathers. we found recurring logs with NGINX errors on the networking-console-plugin and monitoring-console-plugin pods related to missing files, which led us to look into whether this could be contributing to the issue. An example of the logs: 2025-03-31T13:03:39.524580758Z 2025/03/31 13:03:39 [error] 9#9: *128 open() "/opt/app-root/src/locales/sv/plugin__networking-console-plugin.json" failed (2: No such file or directory), client: 10.104.0.147, server: , request: "GET /locales/sv/plugin__networking-console-plugin.json HTTP/1.1", host: "networking-console-plugin.openshift-network-console.svc.cluster.local:9443", referrer: "https://console-openshift-console.apps.openshift-dev.domain.com/k8s/ns/opencost/routes/~new/form" 2025-04-02T07:52:34.863665253Z 2025/04/02 07:52:34 [error] 10#10: *119 open() "/usr/share/nginx/html/locales/sv/plugin__monitoring-plugin.json" failed (2: No such file or directory), client: 10.104.0.147, server: , request: "GET /locales/sv/plugin__monitoring-plugin.json HTTP/1.1", host: "monitoring-plugin.openshift-monitoring.svc.cluster.local:9443", referrer: "https://console-openshift-console.apps.openshift-dev.domain.com/dev-monitoring/ns/opencost/metrics"
Expected results:
The Console must run as expected.