-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18, 4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
cluster:console_plugins_info:max will have two records for one dynamic plugin once the plugin has been disabled once
Version-Release number of selected component (if applicable):
4.18.0-0.nightly-2025-04-17-181105
How reproducible:
Always
Steps to Reproduce:
1. Install some operators which will bring additional dynamic console plugins, such as `Cluster Observerability Operator`, `Kuadrant Operator`, `RedHat OpenShift Pipelines` operator 2. Enable the dynamic plugins in console operator config $ oc get console.operator cluster -o json | jq .spec.plugins [ "monitoring-plugin", "networking-console-plugin", "pipelines-console-plugin", "console-dashboards-plugin", "distributed-tracing-console-plugin", "troubleshooting-panel-console-plugin", "kuadrant-console-plugin" ] 3. Observe -> Metrics, run query against cluster:console_plugins_info:max, 4. Disable some plugins 5. Run the query again
Actual results:
5. There will be two records for the disabled plugin cluster:console_plugins_info:max odf openshift-monitoring/k8s disabled 1 cluster:console_plugins_info:max odf openshift-monitoring/k8s enabled 1 and sometimes it is cluster:console_plugins_info:max odf openshift-monitoring/k8s disabled 1 cluster:console_plugins_info:max odf openshift-monitoring/k8s enabled none
Expected results:
We may probably only show one record for each dynamic plugin to indicate it's current enable/disabled status? What's the purpose of two records? https://github.com/openshift/console/blob/main/pkg/serverconfig/metrics.go#L234-L243
Additional info: