+++ This bug was initially created as a clone of Bug #2141302 +++ Description of problem: Unhealthy states metrics are missing Version-Release number of selected component (if applicable): 4.11 How reproducible: 100% Steps to Reproduce: 1. Create any VMs 2. Check if any KubeVirtVMStuckIn${state}State alerts or kubevirt_vm_${state}_status_last_transition_timestamp_seconds metrics exist Actual results: Metrics and alerts don't exist Expected results: Metrics and alerts exist Additional info: metrics list: kubevirt_vm_error_status_last_transition_timestamp_seconds kubevirt_vm_migrating_status_last_transition_timestamp_seconds kubevirt_vm_non_running_status_last_transition_timestamp_seconds kubevirt_vm_running_status_last_transition_timestamp_seconds kubevirt_vm_starting_status_last_transition_timestamp_seconds alert list: KubeVirtVMStuckInErrorState KubeVirtVMStuckInMigratingState KubeVirtVMStuckInStartingState
For 4.11 release we need to have it backported to release-0.53 of kubevirt
The orginal bug was failed on QE, so we need to fix it again and backport also here.
Do we know if concerns from Roman has been addressed?