Bug 2102724 - Disconnected SRO does not try main registry
Summary: Disconnected SRO does not try main registry
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Special Resource Operator
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: slovern
QA Contact: Constantin Vultur
Tomas 'Sheldon' Radej
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-30 13:38 UTC by Constantin Vultur
Modified: 2022-08-16 02:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Cause: In a disconnected environment SRO doesn't try to fetch the DTK image from the main registry. Consequence: If the needed DTK image isn't available the rebuild of the driver container may fail. Workaround (if any): The DTK image should be hosted in a mirrored, disconnected registry. Result: Successful driver container created.
Clone Of:
Environment:
Last Closed: 2022-08-16 02:48:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Constantin Vultur 2022-06-30 13:38:27 UTC 
Description of problem:
Podman/Crio will always try the main registry and then the mirror(s) registry. 

In case of disconnected cluster, SRO will not try the main registry is not tried at all. So the behavior is different from podma/crio
Giving that, the operator will try to fetch DTK only in the mirror and not on the source registry. 

While the impact is small, I've opened this bug so that this behavior gets documented. 


Version-Release number of selected component (if applicable):
release-4.10 / release-4.11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Brett Thurber 2022-08-02 05:27:34 UTC 
@Costi is this still an issue?
Note You need to log in before you can comment on or make changes to this bug.