Description of problem: When we try to execute recording rules: "kubevirt_vm_container_free_memory_bytes" shows "No datapoints found". This happens since not all VMs have a memory limit set and due to kube_pod_container_resource_limits_memory_bytes metric deprecation in favor of kube_pod_container_resource_limits. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Test kubevirt_vm_container_free_memory_bytes when there is a memory limit set for the VMI container. 2. 3. Actual results: The recording rule returns "No datapoints found" Expected results: The recording rule should have a value Additional info:
PR https://github.com/kubevirt/kubevirt/pull/7052
I am still see "No datapoints found." when execute "kubevirt_vm_container_free_memory_bytes" metrics. Currently cluster is running with --> Deployed: CNV-v4.10.0-641
After adding "memory limits" in the VM spec, I am able to see metrics is showing output. Verifying it.
Bringing back to ON_QA for value validation.
I see recording rule: "kubevirt_vm_container_free_memory_bytes" is using new metrics "https://github.com/kubevirt/kubevirt/pull/7209/files#diff-0f904f2ae31317b82daba8b2976856da054ce0ff43731afe9a91befa5e2489fdR401" I checked the values by executing individual metrics (from above code) and values are approximately correct(free memory is continuously changing).
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 Virtualization 4.10.0 Images security and bug fix 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:0947