+++ This bug was initially created as a clone of Bug #1843058 +++ Description of problem: CAM operator fails to install via the non-olm v1.2.0 operator.yml file that's exported off of the operator image for installation in 3.x clusters. Version-Release number of selected component (if applicable): 1.2.0 How reproducible: Every time Steps to Reproduce: 1. Login to OCP 3.x cluster 2. podman cp $(podman create registry.redhat.io/rhcam-1-2/openshift-migration-rhel7-operator:v1.2):/operator.yml ./ && oc create -f ./operator.yml Actual results: Deployment fails to create with the following error: Error from server (Invalid): error when creating "./operator.yml": Deployment.apps "migration-operator" is invalid: spec.template.spec.containers[1].env[6].name: Required value https://github.com/konveyor/mig-operator/pull/361 shows the problem and the fix, which has been merged to master. Expected results: Operator should install
Issue fixed by the following PR in the release-1.2.1 branch: https://github.com/konveyor/mig-operator/pull/361
Verified in CAM 1.2.1 stage openshift-migration-rhel7-operator@sha256:f9092d108e839bdeec85634e0306c4b9206f391167234058c14386ddfd21b39c Installed in 3.11 without problems. Migrations could be run without problems too.
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/RHBA-2020:2386