Bug 2142918

Summary: Unhealthy states alerts and state metrics are missing
Product: Container Native Virtualization (CNV) Reporter: Krzysztof Majcher <kmajcher>
Component: MetricsAssignee: João Vilaça <jvilaca>
Status: CLOSED DEFERRED QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.11.2CC: dbasunag, jvilaca, ngavrilo, sradco, stirabos
Target Milestone: ---Flags: jvilaca: needinfo?
kmajcher: needinfo-
Target Release: 4.11.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2141302 Environment:
Last Closed: 2023-02-21 14:23:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2141302    
Bug Blocks:    

Description Krzysztof Majcher 2022-11-15 13:47:51 UTC 
+++ 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
Comment 1 Krzysztof Majcher 2022-11-29 13:53:24 UTC 
For 4.11 release we need to have it backported to release-0.53 of kubevirt
Comment 2 Krzysztof Majcher 2022-12-06 13:45:11 UTC 
The orginal bug was failed on QE, so we need to fix it again and backport also here.
Comment 5 Krzysztof Majcher 2023-02-07 13:42:51 UTC 
Do we know if concerns from Roman has been addressed?