tested with the PR, could see the CPU usage graph for deployment, see the attached picture, and "node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate" is replaced by "node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate" # token=`oc sa get-token prometheus-k8s -n openshift-monitoring` # oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://thanos-querier.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate "node_namespace_pod_container:container_cpu_usage_seconds_total:sum_rate",
UI tests for branch release-4.8 are broken (see https://sippy.dptools.openshift.org/sippy-ng/jobs/4.8/analysis?filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22periodic-ci-openshift-release-master-nightly-4.8-console-aws%22%7D%5D%7D), there is a fix in https://github.com/openshift/console/pull/11966 for 4.10 that is being back ported, as seen in that PR automatic cherry pick for 4.8 failed but the team is working on a manual back port
the fix is in 4.8.0-0.nightly-2022-08-29-151822 and later builds, based on comment 3, move the bug to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.8.49 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6308