-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
2
-
False
-
-
False
-
- DataImportCron should use the internal registry on disconnected setups
- No alerts should fire
- KCS article
-
---
-
---
-
-
Storage Core Sprint 238, Storage Core Sprint 245, Storage Core Sprint 252, Storage Core Sprint 255, Storage Core Sprint 256, Storage Core Sprint 257, Storage Core Sprint 258, Storage Core Sprint 259, Storage Core Sprint 261
-
None
In a disconnected OCP cluster, with CNV installed, and golden images enabled, the CDIDataImportCronOutdated alert is constantly firing, because some (or all) of the imported images are not getting mirrored into the disconnected env. This is by design, as these images are not built or owned by the OpenShift Virtualization team. The solution is to disable the mirroring OR to have the customer manually mirror the to be imported images into the disconnected cluster.
Modifying a common dataImportCronTemplate (e.g its source registry url like we need here) is detailed in upstream HCO doc but not in OCP 4.12 doc.
- documents
-
CNV-43540 dataImportCron import is failing when template points to an internal registry that requires authentication
- Closed
- relates to
-
CNV-40722 [RFE] Automatic import of default boot sources support with local registry
- Closed
-
CNV-49139 Document mirroring golden images to disconnected OCP cluster
- New
-
CNV-43540 dataImportCron import is failing when template points to an internal registry that requires authentication
- Closed
- split from
-
CNV-21295 [2127147] CDIDataImportCronOutdated, KubeContainerWaiting, and KubeJobCompletion are constantly firing in a disconnected env
- Closed
- links to