BZ1926248: Manual changes for upgrading MTC 1.3 to 1.4

Author: apinnick

migration/migrating_3_4/upgrading-migration-tool-3-4.adoc

@@ -15,6 +15,9 @@ You must ensure that the same Operator version is installed on the source and ta
 Do not enable automatic updates on the {product-title} {product-version} cluster.
 ====
 
+If you are upgrading {mtc-short} 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
+
 include::modules/migration-upgrading-migration-tool-4.adoc[leveloffset=+1]
 include::modules/migration-upgrading-migration-tool-3.adoc[leveloffset=+1]
+include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+1]
 :migrating-3-4!:

migration/migrating_4_1_4/upgrading-migration-tool-4-1-4.adoc

@@ -8,5 +8,8 @@ toc::[]
 
 You can upgrade the {mtc-full} ({mtc-short}) by upgrading the {mtc-full} Operator.
 
+If you are upgrading {mtc-short} 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
+
 include::modules/migration-upgrading-migration-tool-4.adoc[leveloffset=+1]
+include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+1]
 :migrating-4-1-4!:

migration/migrating_4_2_4/upgrading-migration-tool-4-2-4.adoc

@@ -8,5 +8,8 @@ toc::[]
 
 You can upgrade the {mtc-full} ({mtc-short}) by upgrading the {mtc-full} Operator.
 
+If you are upgrading {mtc-short} 1.3, you must perform an additional procedure to update the `MigPlan` custom resource (CR).
+
 include::modules/migration-upgrading-migration-tool-4.adoc[leveloffset=+1]
+include::modules/migration-upgrading-from-mtc-1-3.adoc[leveloffset=+1]
 :migrating-4-2-4!:

modules/migration-upgrading-from-mtc-1-3.adoc

@@ -0,0 +1,50 @@
+// Module included in the following assemblies:
+// * migration/migrating_3_4/upgrading-migration-tool-3-4.adoc
+// * migration/migrating_4_1_4/upgrading-migration-tool-4-1-4.adoc
+// * migration/migrating_4_2_4/upgrading-migration-tool-4-2-4.adoc
+
+[id="migration-upgrading-from-mtc-1-3_{context}"]
+= Upgrading {mtc-short} 1.3
+
+If you are upgrading {mtc-full} ({mtc-short}) version 1.3.x, you must manually update the `indirectImageMigration` and `indirectVolumeMigration` parameters in the `MigPlan` custom resource (CR).
+
+Because the `indirectImageMigration` and `indirectVolumeMigration` parameters do not exist in version 1.3, their default value in version 1.4 is `false`, which means that direct image migration and direct volume migration are enabled. Because the direct migration requirements are not fulfilled, the migration plan cannot reach a `Ready` state unless these parameter values are changed to `true`.
+
+.Prerequisites
+
+* You must have upgraded {mtc-short} from version 1.3.x to 1.4.
+* You must have `cluster-admin` privileges.
+
+.Procedure
+
+. Log in to the target cluster.
+. Get the `MigPlan` CR:
++
+[source,terminal]
+----
+$ oc get migplan <migplan> -o yaml -n openshift-migration
+----
+
+. Change the following parameter values to `true` and save the file:
++
+[source,yaml]
+----
+...
+spec:
+  indirectImageMigration: true
+  indirectVolumeMigration: true
+----
+
+. Apply the changes:
++
+[source,terminal]
+----
+$ oc replace -f <migplan>.yaml -n openshift-migration
+----
+
+. Verify the changes by viewing the updated `MigPlan` CR:
++
+[source,terminal]
+----
+$ oc get migplan <migplan> -o yaml -n openshift-migration
+----