Closed alexgdmx closed 2 months ago
I think this is unrelated but when I searched for failed dynamic plugins this issue came up. A hard refresh of the browser solved the issue for me. https://access.redhat.com/solutions/7052408
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
@openshift-bot: Closing this issue.
Extending this issue https://github.com/openshift/console/issues/13569
In my case, ODF is always working and never fails.
Dynamic plugins: [kubevirt-plugin, mce, monitoring-plugin, nmstate-console-plugin, odf-console, acm] vendorsmain-chunk-fa66b5f55415df590be0.min.js:30874 react-i18next:: It seems you are still using the old wait option, you may migrate to the new useSuspense behaviour. . . . main-chunk-d5cd4d073a730b8d448a.min.js:1 destroying websocket: /api/kubernetes/api/v1/namespaces/openshift-console-user-settings/configmaps?watch=true&fieldSelector=metadata.name%3Duser-settings-kubeadmin&cluster=local-cluster 8WebSocket connection to '' failed: WebSocket is closed before the connection is established. main-chunk-d5cd4d073a730b8d448a.min.js:1
Even when is loaded there are many js errors
Definitely, the console pods are not processing well the plugins, all plugging pods responded with a well-formed json
Monitoring pod plugins is responding well
sh-4.4$ curl -k https://localhost:9443/plugin-manifest.json { "name": "monitoring-plugin", "version": "1.0.0", "displayName": "OpenShift console monitoring plugin", "description": "This plugin adds the monitoring UI to the OpenShift web console", "dependencies": { "@console/pluginAPI": "*" }, "extensions": [ { "type": "console.page/route", "properties": { "exact": true, "path": "/monitoring", "component": { "$codeRef": "MonitoringUI" } } },
MCE responded well
sh-4.4$ curl -k https://localhost:3000/plugin/plugin-manifest.json { "name": "mce", "version": "2.4.0", "displayName": "multicluster engine for Kubernetes", "description": "Integrates multicluster engine for Kubernetes functionality into the OpenShift Container Platform web console", "dependencies": { "@console/pluginAPI": "*" }, "extensions": [ { "type": "console.context-provider", "properties": {
kubevirt-plugin responded well also
sh-5.1$ curl -k https://localhost:9443/plugin-manifest.json { "name": "kubevirt-plugin", "version": "0.0.0", "displayName": "Kubevirt Plugin", "dependencies": { "@console/pluginAPI": "*" }, "extensions": [ { "properties": { "handler": { "$codeRef": "kubevirtFlags.enableKubevirtDynamicFlag" }
NMSTATE plugin pod
[alex@bastion ~]$ oc rsh nmstate-console-plugin-bdb5579bd-sxz7g sh-4.4$ curl -k https://localhost:9443/plugin-manifest.json { "name": "nmstate-console-plugin", "version": "0.0.1", "displayName": "OpenShift Console Plugin For NMState", "description": "NMState is a library that manages host netowrking settings in a declarative manner.", "dependencies": { "@console/pluginAPI": "*" }, "extensions": [