Bug 1868763

Summary:	VERIFY CAM disconnected installation and usage in a true disconnected environment
Product:	Migration Toolkit for Containers	Reporter:	Erik Nelson <ernelson>
Component:	General	Assignee:	John Matthews <jmatthew>
Status:	ON_QA ---	QA Contact:	Xin jiang <xjiang>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	1.3.0	CC:	chezhang, jmatthew, sregidor, whu
Target Milestone:	---
Target Release:	1.3.z
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:		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 Erik Nelson 2020-08-13 18:34:09 UTC

Description of problem:
A bug was discovered in the stage pod code that revealed the stage pod was hardcoded to use a registry.access.redhat.com pullspec: https://bugzilla.redhat.com/show_bug.cgi?id=1867597

This suggests that truly disconnected installation and usage of CAM has never actually been exercised.

This BZ is intended to track the work involved in VERIFYing CAM disconnected functions as expected. This requires the set up of a disconnected environment, perhaps an AWS deployment without external network access and two clusters that have functional networking between the two of them. Then we need to confirm that the current disconnected documentation is accurate: https://github.com/konveyor/mig-operator/blob/master/docs/usage/DisconnectedDeployment.md

Version-Release number of selected component (if applicable):
1.2.4

Comment 2 Xin jiang 2020-08-17 02:27:05 UTC

In order to setup the environment, it seems we need to to take a look at "Installing a cluster on AWS into an existing VPC" https://docs.openshift.com/container-platform/4.3/installing/installing_aws/installing-aws-vpc.html