Loading...

XML

Word

Printable

Regression:
None
Sprint:
CLID Sprint 267
sprint_count:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
What: if there were failures getting kubevirt and graphImage images, they were being skipped.
Consequence: the overall oc-mirror run would succeed but the images would be missing even though they were requested in the ImageSetConfiguration file.
Fix: now oc-mirror run fails when the images are not found.

Show
What: if there were failures getting kubevirt and graphImage images, they were being skipped. Consequence: the overall oc-mirror run would succeed but the images would be missing even though they were requested in the ImageSetConfiguration file. Fix: now oc-mirror run fails when the images are not found.
Release Note Type:
Bug Fix
Release Note Status:
In Progress
Target Version:

4.18.0
Target Backport Versions:

4.18.0

This is a clone of issue OCPBUGS-49990. The following is the description of the original issue:
—
Description of problem:

    During the collection, the KubeVirt image and the OSUS (graph image) are being skipped in case of failure to find them.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

 Check the local_store_collector.go on the release package

Actual results:

    Images are skipped

Expected results:

    If the image was requested in the image set config, since these are release images, they should not be skipped, the workflow should fail

Additional info:

clones

OCPBUGS-49990 Kubevirt and OSUS image skipped in collection phase

is blocked by

OCPBUGS-49990 Kubevirt and OSUS image skipped in collection phase

links to