Description of problem: SSIA Version-Release number of selected component (if applicable): 1.4.2 How reproducible: Every time Steps to Reproduce: 1. Run through breakfix exercise 3: https://github.com/konveyor/mtc-breakfix/tree/master/03-Gvk Actual results: No warning is reported, and the underlying CR is never migrated. Expected results: Either a GVK diff should have picked this up and warned, or the migration should have failed. We had previous behavior in place to handle a diff like this and this appears to be a regression in that behavior.
We believe this to have been fixed such that the exercise will raise a warning as of MTC 1.5.0 due to our rebase onto the latest Velero release. The expectation is that a warning should be raised, we're looking to verify this to be true through QE.
As Erik explained above, with Velero v1.6, we will see both warning and error in the Restore CR. The expected behavior is NOT changed, its just that minor semantics around finding the logs are changed. But apart from that, QE shoudl be able to verify the behavior as explained in the breakfix doc.
Verified using MTC 1.5.0 openshift-migration-rhel7-operator@sha256:00e77706ca22bcb557d13c16822180fc877e6ea1639a72fda8eb9f5488b039a2 - name: MIG_CONTROLLER_REPO value: openshift-migration-controller-rhel8@sha256 - name: MIG_CONTROLLER_TAG value: 7f657df15e9514df4ef42da3431f558a19b8d3233a2ef1222cd8e27793c93816 Azure 4.4 -> Azure 4.8, Azure storage class The Restore part of the migration fails with the error 'level=error msg="error restoring gvk-demo: the server could not find the requested resource"' and the migmigration resource shows a warning. The migplan is displayed in the UI as "Migration completed with warnings". This is the right behavior, we move the BZ to VERIFIED.
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) image release advisory 1.5.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/RHEA-2021:2929