-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
0.42
-
False
-
-
False
-
CNV v4.99.0.rhel9-665, CNV v4.17.0.rhel9-164
-
---
-
---
-
-
1
-
CNV I/U Operators Sprint 255, CNV I/U Operators Sprint 256, CNV I/U Operators Sprint 257
-
No
Description of problem:
KubeVirtVMIExcessiveMigrations calculation is wrong $ oc get vmim -n demo-cluster-disco NAME PHASE VMI kubevirt-evacuation-4xccc Succeeded bastion kubevirt-evacuation-ttfgk Succeeded bastion kubevirt-evacuation-x7tbs Succeeded bastion kubevirt-workload-update-9t686 Succeeded bastion kubevirt-workload-update-s9b7s Succeeded bastion
Version-Release number of selected component (if applicable):
kubevirt-hyperconverged-operator.v4.15.0 OCP 4.15.8
How reproducible:
Always after cluster upgrade I get the alert.
Steps to Reproduce:
1. 2. 3.
Actual results:
Fire KubeVirtVMIExcessiveMigrations alert
Expected results:
It should because there are not >12 migration in last 24h
Additional info:
It's a red hat internal cluster I can provide access.
- is cloned by
-
-
- Closed
-
- links to
-
RHEA-2024:133097
OpenShift Virtualization 4.17.0 Images
- mentioned on
(12 mentioned on)