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

Bug 1843058

Summary: CAM operator fails to install via non-olm v1.2.0 operator.yml file
Product: OpenShift Container Platform Reporter: Erik Nelson <ernelson>
Component: Migration ToolingAssignee: Erik Nelson <ernelson>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: chezhang, mberube, rjohnson, sregidor, whu
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1843059 (view as bug list) Environment:
Last Closed: 2020-09-30 18:42:29 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:
Bug Depends On:    
Bug Blocks: 1843059    

Description Erik Nelson 2020-06-02 16:49:13 UTC
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

Comment 3 Xin jiang 2020-09-16 06:39:22 UTC
verified with MTC 1.3.0
$ oc get pod -n openshift-migration migration-operator-7ffd8bcf69-6g5x7 -o yaml | grep image
    image: quay-enterprise-quay-enterprise.apps.cam-tgt-8380.qe.devcluster.openshift.com/admin/openshift-migration-rhel7-operator:v1.3
    imagePullPolicy: Always
  imagePullSecrets:
    image: quay-enterprise-quay-enterprise.apps.cam-tgt-8380.qe.devcluster.openshift.com/admin/openshift-migration-rhel7-operator:v1.3
    imageID: docker-pullable://quay-enterprise-quay-enterprise.apps.cam-tgt-8380.qe.devcluster.openshift.com/admin/openshift-migration-rhel7-operator@sha256:80c1345afa8bee9e9afe7bb83709a320e56b2febef49b3174a2188f90a4dfa9b

Comment 7 errata-xmlrpc 2020-09-30 18:42:29 UTC
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 (Migration Toolkit for Containers (MTC) Tool image release advisory 1.3.0), 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:4148