Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ACM, Kubevirt-plugin, MCE, monitoring-plugin, nmstate-console-plugin Failed state #13581

Open
alexgdmx opened this issue Feb 6, 2024 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@alexgdmx
Copy link

alexgdmx commented Feb 6, 2024

Extending this issue https://github.com/openshift/console/issues/13569

In my case, ODF is always working and never fails.

Screenshot 2024-02-06 at 2 07 24 AM

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

Screenshot 2024-02-06 at 2 30 45 AM

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": [

@paddy667
Copy link

paddy667 commented Feb 14, 2024

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

@openshift-bot
Copy link
Contributor

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants