-
Bug
-
Resolution: Done-Errata
-
Normal
-
CNV v4.19.0, CNV v4.18.z
-
Quality / Stability / Reliability
-
8
-
False
-
-
False
-
CNV v4.19.0.rhel9-107
-
-
None
Description of problem:
When the kubevirt storage checkup is executed from the UI, a job is created and it uses the upstream image: quay.io/kiagnose/kubevirt-storage-checkup:main instead of the downstream one that we're building in the bundle at every release.
Version-Release number of selected component (if applicable):
4.14 - 4.19
How reproducible:
100%
Steps to Reproduce:
1. In the UI, navigate to Virtualization --> Checkups 2. Click on the storage tab 3. Run Checkup, set name, and Run 4. Observe the job object that was generated 5. Examine the image it uses - it's quay.io/kiagnose/kubevirt-storage-checkup:main and it should be taken from registry.redhat.io according to the installed CNV version.
Actual results:
the job uses an hard-coded image from upstream main
Expected results:
the job should be using the downstream image we ship in the bundle:
registry.redhat.io/container-native-virtualization/kubevirt-storage-checkup-rhel9:v4.Y
this image is available for Y = {16,17,18} at the moment. 19 will be available on CNV 4.19.0 GA
Additional info:
- is related to
-
CNV-57954 kubevirt network latency checkup in the UI uses a 4.13 image for all versions
-
- Closed
-
- links to
-
RHEA-2025:145122
OpenShift Virtualization 4.19.0 Images
- mentioned on
(2 mentioned on)