Description of problem: Currently, the migration registry (used for copying internal image from source to target cluster) is launched using the upstream "registry:2" image. This should be made configurable, to allow for disconnected installations and to remove the dependency on upstream external image availability Version-Release number of selected component (if applicable): 4.2.z How reproducible: Always Steps to Reproduce: 1. Open a migplan 2. Note the location of the migration registry image 3. Actual results: Migration registry image comes from "registry:2" (docker.io) Expected results: Migration registry image comes from configured location Additional info:
controller commit https://github.com/fusor/mig-controller/commit/51060bd15dc1abf5b34be705ebca2e1f8920b037 operator PR: https://github.com/fusor/mig-operator/pull/224
Verified in CAM 1.1 stage Now registry pods are using the new registry image oc get pods -o yaml registry-ocp24797-mongodb-migplan-1580734111-f6ch8-1-nqtsp | grep image image: registry.stage.redhat.io/rhcam-1-1/openshift-migration-registry-rhel8@sha256:0ae610db4f73b6a5353c4821165bd60a8c4e86ac5ba5f1d60cd532f5bcd814bd imagePullPolicy: IfNotPresent And can be reconfigured to use any other image, for instance the docker.io one Adding to the controller spec migration_registry_image: docker.io/registry migration_registry_repo: registry migration_registry_version: 2 oc get pods -o yaml registry-ocp-25212-initcont-migplan-1580739992-vmgrn-1-v2bf6 | grep imageID imageID: docker.io/library/registry@sha256:3a8eef8d0a818b9bbb4bd17667253473e2d99935ccbbd37649af6bcaa064cf0d
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0440