-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
3
-
False
-
False
-
CLOSED
-
CNV I/U Operators Sprint 220, CNV Virtualization Sprint 216, CNV Doc Sprint 217, CNV I/U Operators Sprint 222
-
High
-
None
Description of problem: Created several VM's and run metric "kubevirt_num_virt_handlers_by_node_running_virt_launcher" and saw that the value reported is corresponding to the no. of "virt-launcher" pods available on node.
Version-Release number of selected component (if applicable):4.10
How reproducible:100%
Steps to Reproduce:
1. Create 2-3 Virtual Machines.
2. Run/execute metrics "kubevirt_num_virt_handlers_by_node_running_virt_launcher"
3.
Actual results: Metrics showing values of virt-laucher pods
Expected results: It should show virt-handler pod values.
Additional info:
- external trackers
(4 external trackers)