-
Bug
-
Resolution: Unresolved
-
Normal
-
CNV v4.18.0
-
None
-
Quality / Stability / Reliability
-
5
-
False
-
-
False
-
CNV v4.99.0.rhel9-2444, CNV v4.21.0.rhel9-31
-
-
CNV Virt-Cluster Sprint 267, CNV Virt-Cluster Sprint 273, CNV Virt-Cluster Sprint 274, CNV Virt-Cluster Sprint 275, CNV Virt-Cluster Sprint 276, CNV Virt-Cluster Sprint 277, CNV Virt-Cluster Sprint 278, CNV Virt-Cluster Sprint 279
-
None
Description of problem:
Every time CNV (or kubevirt in general) is upgraded, a new kubevirt-install-strategy config map is being created, which contains a binary, gzipped data of a very not negligible size (>400KB), and it is not cleaned up after subsequent upgrades on the same cluster. This results in non-relevant resources stacked up on the openshift-cnv namespace without any use, which overloads the etcd for no good reason.
Version-Release number of selected component (if applicable):
All versions since the very beginning
How reproducible:
100%
Steps to Reproduce:
1. Have CNV installed on the cluster 2. Observe there is a kubevirt-install-strategy config map in the installation namespace (openshift-cnv) 3. Upgrade CNV
Actual results:
Notice a new kubevirt-install-strategy config map was created, and the old one is still there.
Expected results:
the old, obsolete and irrelevant kubevirt-install-strategy CM should be removed automatically.
Additional info:
- links to
-
RHEA-2025:155516
OpenShift Virtualization 4.21.0 Images
- mentioned on
