-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
8
-
False
-
-
False
-
OCPSTRAT-1299 - [Tech Preview][Phase2] Enclave Support for oc-mirror
-
---
-
---
-
-
-
CLID Sprint 256, CLID Sprint 257, CLID Sprint 258, CLID Sprint 259, CLID Sprint 260
-
No
It is necessary to create a data structure that contains in which operator each related image is encountered, it is possible to get this information from the current loop already present in the collection phase.
Having this data structure will allow to tell customers which operators failed based on a image that failed during the mirroring.
For example: related image X failed during the mirroring, this related image is present in the operators a, b and c, so in the mirroring errors file already being generated is going to include the name of the operators instead of the name of the related image only.
- for a fail safe on a related image, stop mirroring the whole group of related images for that bundle
- AND especially, defer mirroring bundle images till all related images are mirrored. Otherwise, we'll be in the situation you described yesterday: the operator starts upgrading when its related images are missing
- is documented by
-
CLID-133 As a developer I want to define which operator failed during mirroring
- Closed
- links to