Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1946865

Summary: no "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: MonitoringAssignee: Jan Fajerski <jfajersk>
Status: CLOSED ERRATA QA Contact: hongyan li <hongyli>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.8CC: alegrand, anowak, anpicker, erooth, kakkoyun, lcosic, pkrupa, spasquie
Target Milestone: ---Keywords: Regression
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:57:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
no "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics none

Description Junqi Zhao 2021-04-07 04:33:46 UTC 
Created attachment 1769750 [details]
no "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics

Created attachment 1769750 [details]
no "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics

Description of problem:
"Kubernetes / Compute Resources / Cluster" dashboard, no result for "CPU Requests Commitment" and "Memory Requests Commitment", on UI, the result shows "-"
click inspect to check
"CPU Requests Commitment" expression is
sum(namespace:kube_pod_container_resource_requests_cpu_cores:sum{cluster=""}) / sum(kube_node_status_allocatable{resource="cpu",cluster=""})

"Memory Requests Commitment" expression is
sum(namespace:kube_pod_container_resource_requests_memory_bytes:sum{cluster=""}) / sum(kube_node_status_allocatable{resource="memory",cluster=""})

checked, there is not "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics in cluster
only "kube_pod_container_resource_requests_cpu_cores" and "kube_pod_container_resource_requests_memory_bytes" exist
# 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://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep kube_pod_container_resource_requests_cpu_cores
    "kube_pod_container_resource_requests_cpu_cores",

# oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/label/__name__/values' | jq | grep kube_pod_container_resource_requests_memory_bytes
    "kube_pod_container_resource_requests_memory_bytes",



Version-Release number of selected component (if applicable):
4.8.0-0.nightly-2021-04-06-162113

How reproducible:
always

Steps to Reproduce:
1. Go to admin console, "Monitoring - > Dashboard", choose "Kubernetes / Compute Resources / Cluster" dashboard
2.
3.

Actual results:
there is not "namespace:kube_pod_container_resource_requests_cpu_cores:sum" and "namespace:kube_pod_container_resource_requests_memory_bytes:sum" metrics in cluster

Expected results:


Additional info:
Comment 1 Junqi Zhao 2021-04-07 04:42:14 UTC 
there are cpu/memory request for containers, example
# for i in $(kubectl -n openshift-monitoring get po --no-headers | awk '{print $1}'); do echo $i; kubectl -n openshift-monitoring get pod $i -o go-template='{{range.spec.containers}}{{"Container Name: "}}{{.name}}{{"\r\nresources: "}}{{.resources}}{{"\n"}}{{end}}'; echo -e "\n"; done
alertmanager-main-0
Container Name: alertmanager
resources: map[requests:map[cpu:4m memory:200Mi]]
Container Name: config-reloader
resources: map[requests:map[cpu:1m memory:10Mi]]
Container Name: alertmanager-proxy
resources: map[requests:map[cpu:1m memory:20Mi]]
Container Name: kube-rbac-proxy
resources: map[requests:map[cpu:1m memory:20Mi]]
Container Name: prom-label-proxy
resources: map[requests:map[cpu:1m memory:20Mi]]
Comment 7 hongyan li 2021-05-06 07:07:16 UTC 
Test with payload 4.8.0-0.nightly-2021-05-06-003426

"Kubernetes / Compute Resources / Cluster" dashboard, results are correct for "CPU Requests Commitment" and "Memory Requests Commitment"
click inspect to check
"CPU Requests Commitment" expression is
sum(namespace_cpu:kube_pod_container_resource_requests:sum{cluster=""}) / sum(kube_node_status_allocatable{resource="cpu",cluster=""})

"Memory Requests Commitment" expression is
sum(namespace_memory:kube_pod_container_resource_requests:sum{cluster=""}) / sum(kube_node_status_allocatable{resource="memory",cluster=""})
Comment 10 errata-xmlrpc 2021-07-27 22:57:54 UTC 
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and 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-2021:2438