Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: This is a regression and a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1886125. Essentially, the imagetag plugin in the openshift velero plugin is being applied to all resources in 4.3 and below due to the imagetag CRD not existing in the cluster. Version-Release number of selected component (if applicable): MTC 1.4 How reproducible: 100% Steps to Reproduce: 1. Migrate from OCP 3.11 to OCP 4.3 Actual results: In the velero pod on the destination cluster the logs show every resources is being discarded by the imagetag plugin. Expected results: Migration succeeds. Additional info: The actual issue is an upstream bug where if a plugin is registered with Velero and the associated CRD doesn't exist, every resource matches the plugin. This may or may not be resolved upstream in Velero yet I need to dig further. For 1.4.0 we will simply remove the imagetag plugin from the openshift plugin as we did for 1.3.
https://github.com/konveyor/openshift-velero-plugin/pull/70
Verified using: - MTC 1.4.0 - 3.11 -> 4.3 AWS, AWS S3 - 4.5 -> 4.7 AWS, AWS S3 openshift-migration-rhel7-operator@sha256:085a42a4bdf32cd0ae12cb5af17d6ee6274a577a67298708a2eff3220e08fc23 - name: MIG_CONTROLLER_REPO value: openshift-migration-controller-rhel8@sha256 - name: MIG_CONTROLLER_TAG value: 5590dc251338f1d909bb6c76722d251c5de114c272d6425455549623a5472c4d Moved to VERIFIED status.
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