Description of problem: It does specify "migration_log_reader: true" in MigrationController, but there is no migration-log-reader pod created in 3.x cluster Version-Release number of selected component (if applicable): MTC 1.4.0 Images: "brew.registry.redhat.io/rhmtc/openshift-migration-rhel7-operator@sha256:61de8be7e30fb15b278aeececb0de8ac5ecaeb221a312ab1140e6c925ab0e217", "brew.registry.redhat.io/rhmtc/openshift-migration-velero-plugin-for-aws-rhel8@sha256:681400269fc880f228011bc20a9dc19dc88f81e063daafdf6b377707ad2b1c86", "brew.registry.redhat.io/rhmtc/openshift-migration-velero-plugin-for-gcp-rhel8@sha256:5ad17bb5fd19685316211149ee859c8446415de8a5a11f71eb3a823344803a38", "brew.registry.redhat.io/rhmtc/openshift-migration-velero-plugin-for-microsoft-azure-rhel8@sha256:ee0e58f8aa4ce267f06843d7b823705ec7253749c91040e5a066861bdc4cd599", "brew.registry.redhat.io/rhmtc/openshift-migration-velero-rhel8@sha256:e64834303fc4bbe88f780e3801359abf45121092cd57b14876f896ac9fa4f640", "brew.registry.redhat.io/rhmtc/openshift-velero-plugin-rhel8@sha256:e078a27ce802da8ffbe409d4e1f602c4813af0bd81c8609661c55ac6ac210902" How reproducible: Always Steps to Reproduce: When the MTC is installed 3.11 OCP cluster, I found 2 issues: 1) migration-log-reader pod is not created 2) migration-controller SA is not created $ oc version oc v3.11.126 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ec2-54-84-148-89.compute-1.amazonaws.com:8443 openshift v3.11.318 kubernetes v1.11.0+d4cacc0 $ oc get pod -n openshift-migration NAME READY STATUS RESTARTS AGE migration-operator-7774cc5dff-2rqtx 1/1 Running 0 1h restic-42vcm 1/1 Running 0 1h restic-89rfm 1/1 Running 0 1h restic-gnghc 1/1 Running 0 1h restic-grl75 1/1 Running 0 1h restic-s6mlg 1/1 Running 0 1h restic-vd9sv 1/1 Running 0 1h restic-w4wtt 1/1 Running 0 1h velero-64776b667b-qb94f 1/1 Running 0 1h $ oc get sa -n openshift-migration NAME SECRETS AGE builder 2 1h default 2 1h deployer 2 1h migration-operator 2 1h velero 2 1h Actual results: It misses migration-log-reader pod and migration-controller SA under openshift-migration namespace Expected results: migration-log-reader pod and migration-controller SA should be created under openshift-migration namespace Additional info:
The CRD task is failing preventing much of the role tasks from running: PLAY RECAP ********************************************************************* localhost : ok=16 changed=0 unreachable=0 failed=1 skipped=18 rescued=0 ignored=0 /opt/ansible/roles/migrationcontroller/tasks/main.yml:201 A PR was put in to rename the CRD files and it looks like an 'e' was dropped from one of the filenames.
verified. $ oc version oc v3.11.126 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ec2-54-81-116-16.compute-1.amazonaws.com:8443 openshift v3.11.346 kubernetes v1.11.0+d4cacc0 $ oc get pod -n openshift-migration NAME READY STATUS RESTARTS AGE migration-log-reader-9c95557f8-r4ttx 2/2 Running 0 21h migration-operator-546d55f657-557fj 1/1 Running 0 21h Operator image: image: brew.registry.redhat.io/rhmtc/openshift-migration-rhel7-operator@sha256:236d5f964061938f4e845e6d9e62926da68435c0f0304329a0473e060cdb53f1
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.4.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:5329