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

Bug 1885557

Summary:	[RFE] Allow STF to be installed in a disconnected environment
Product:	Service Telemetry Framework	Reporter:	Mohammed Salih <mputhenp>
Component:	distribution	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED MIGRATED	QA Contact:	Alex Yefimov <ayefimov>
Severity:	high	Docs Contact:	mgeary <mgeary>
Priority:	high
Version:	1.1	CC:	alolivei, asimonel, augol, chrisbro, cylopez, dhill, jjoyce, jseunghw, jveiraca, ldenny, lmadsen, mburns, mburrows, mmagr, mrunge, scohen, shrjoshi, shtiwari, sputhenp, yocha
Target Milestone:	z4	Keywords:	FutureFeature, Triaged
Target Release:	1.5 (STF)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 19:26: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 Mohammed Salih 2020-10-06 12:04:06 UTC

Description of problem:
Could not deploy Service Telemtry Framework in a disconnected OpenShift environment. This could be a RFI bug , but it could be a requirement from almost all Telcos who doesn't want to connect their cloud to internet.

Version-Release number of selected component (if applicable):
Red Hat OpenStack 13

How reproducible:
Always.

Steps to Reproduce:
1. Deploy OpenShift in a disconnected network. Follow the doc here . https://docs.openshift.com/container-platform/4.4/welcome/index.html
2. Create a local Operator hub using this doc https://docs.openshift.com/container-platform/4.4/operators/olm-restricted-networks.html
3. Follow https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/service_telemetry_framework/index to start deploying STF in OpenShift.
4. Create a local repository for Community Operator hub catalog using similar procedures outlined in the "Create a local Operator hub doc"
5. Try to subscribe to the AMQ Certificate Manager Operator (section 2.3.7) from redhat-operator hub. Subscription works but it won't be able to pull container images from the local repositories.

My thought on this issue is that, though I have a `ImageContentSourcePolicy` setup in OpenShift and points to the local repository as mirror, the operator is looking for container images with a tag instead of digest. But as per the disconnected OLM documentation all image References should be by a digest (SHA) and not by a tag.

So in-order to satisfy the requirements of disconnect OLM deployment all the STF operators needs to be updated to point to digests instead of tags.

Actual results:
AMQ Cert Manager operator deployment fails. Haven't tried other operators, but most probably they will have the same fate.

Expected results:
STF deployed in a disconnected OpenShift environment using a disconnected OLM.

Additional info:

Comment 1 Leif Madsen 2020-10-06 13:17:10 UTC

I'm targeting this for STF 1.2. Will need to coordinate with other teams likely and do some testing to identify all the Operators that might need to be adjusted.

Comment 2 Mohammed Salih 2020-10-08 06:00:07 UTC

So far I could locate the following containers with tags 

stf/service-telemetry-rhel7-operator:1.0.3
stf/smart-gateway-rhel7-operator:2.0.1
stf/smart-gateway-rhel8:2.0.1
stf/sg-core-rhel8:3.0.0
stf/sg-bridge-rhel8:1.0.0
amq7/amq-cert-manager:1.0
amq7/amq-interconnect:1.8

I think Prometheus uses digest instead of tags. I haven't tried installing Elasticsearch yet, probably it also has the same issue.

Comment 3 Leif Madsen 2020-10-09 15:54:32 UTC

Note that at lest the AMQ Interconnect operator is not disconnected compatible, per https://access.redhat.com/articles/4740011

For STF 1.1 the CSV should be closer to supporting a disconnected installation in OCP 4.5. We're adding the `relatedImages` and linking all container images to the sha256 hash as the tag vs the named tag.

I also haven't checked the ElasticSearch (ECK) operator.

Comment 9 ldenny 2021-07-19 22:52:27 UTC

Hi Leif,

Is there any current work around for installing STF in a disconnected environment or do we need to wait until this RFE has been complete?

Comment 10 Leif Madsen 2021-07-20 03:27:00 UTC

This work is not yet scheduled, but I expect it to move up in priority. At this time there has not been a scoping effort or assignment for this RFE.

Comment 22 Leif Madsen 2023-08-04 00:12:26 UTC

Status update:

Investigations ongoing. Depends on fully-supported stack which means all components are available from the Red Hat Operators CatalogSource as support for a fully disconnected installation is dependent on components we do not control. Target early-mid 2024.