Bug 1868763 - VERIFY CAM disconnected installation and usage in a true disconnected environment
Summary: VERIFY CAM disconnected installation and usage in a true disconnected environ...
Keywords:
Status: ON_QA
Alias: None
Product: Migration Toolkit for Containers
Classification: Red Hat
Component: General
Version: 1.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 1.3.z
Assignee: John Matthews
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-13 18:34 UTC by Erik Nelson
Modified: 2022-08-10 06:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.