Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2102724

Summary:	Disconnected SRO does not try main registry
Product:	OpenShift Container Platform	Reporter:	Constantin Vultur <cvultur>
Component:	Special Resource Operator	Assignee:	slovern <slovern>
Status:	CLOSED WONTFIX	QA Contact:	Constantin Vultur <cvultur>
Severity:	high	Docs Contact:	Tomas 'Sheldon' Radej <tradej>
Priority:	high
Version:	4.11	CC:	bthurber
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-16 02:48:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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?