Chapter 6. Upgrading the Migration Toolkit for Containers

Procedure

1. In the OpenShift Container Platform console, navigate to Operators Installed Operators.

   Operators that have a pending upgrade display an Upgrade available status.

2. Click Migration Toolkit for Containers Operator.
3. Click the Subscription tab. Any upgrades requiring approval are displayed next to Upgrade Status. For example, it might display 1 requires approval.
4. Click 1 requires approval, then click Preview Install Plan.
5. Review the resources that are listed as available for upgrade and click Approve.
6. Navigate back to the Operators Installed Operators page to monitor the progress of the upgrade. When complete, the status changes to Succeeded and Up to date.
7. Click Workloads Pods to verify that the MTC pods are running.

Procedure

1. Log in to registry.redhat.io with your Red Hat Customer Portal credentials:

   $ sudo podman login registry.redhat.io

2. Download the latest operator.yml file:

   $ sudo podman cp $(sudo podman create \
     registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/operator.yml ./ 1

   1

   You can specify a z-stream release, if necessary.

3. Replace the Migration Toolkit for Containers Operator:

   $ oc replace --force -f operator.yml

4. Apply the changes:

   • For MTC 1.1.2 and earlier versions, delete the Restic pods:

     $ oc delete pod <restic_pod>

   • For MTC 1.2 and later versions:

     1. Scale the migration-operator deployment to 0 to stop the deployment:

        $ oc scale -n openshift-migration --replicas=0 deployment/migration-operator

     2. Scale the migration-operator deployment to 1 to start the deployment and apply the changes:

        $ oc scale -n openshift-migration --replicas=1 deployment/migration-operator

5. Verify that the migration-operator was upgraded:

   $ oc -o yaml -n openshift-migration get deployment/migration-operator | grep image: | awk -F ":" '{ print $NF }'

6. Download the latest controller-3.yml file:

   $ sudo podman cp $(sudo podman create \
     registry.redhat.io/rhmtc/openshift-migration-rhel7-operator:v1.4):/controller-3.yml ./

7. Create the migration-controller object:

   $ oc create -f controller-3.yml

8. If your OpenShift Container Platform version is 3.10 or earlier, set the security context constraint of the migration-controller service account to anyuid to enable direct image migration and direct volume migration:

   $ oc adm policy add-scc-to-user anyuid -z migration-controller -n openshift-migration

9. Verify that the MTC pods are running:

   $ oc get pods -n openshift-migration

10. If you have previously added the OpenShift Container Platform 3 cluster to the MTC web console, you must update the service account token in the web console because the upgrade process deletes and restores the openshift-migration namespace:

    1. Obtain the service account token:

       $ oc sa get-token migration-controller -n openshift-migration

    2. In the MTC web console, click Clusters.
    3. Click the Options menu next to the cluster and select Edit.
    4. Enter the new service account token in the Service account token field.
    5. Click Update cluster and then click Close.

Procedure

1. Log in to the cluster on which the MigrationController pod is running.

2. Get the MigPlan CR manifest:

   $ oc get migplan <migplan> -o yaml -n openshift-migration

3. Update the following parameter values and save the file as migplan.yaml:

   ...
   spec:
     indirectImageMigration: true
     indirectVolumeMigration: true

4. Replace the MigPlan CR manifest to apply the changes:

   $ oc replace -f migplan.yaml -n openshift-migration

5. Get the updated MigPlan CR manifest to verify the changes:

   $ oc get migplan <migplan> -o yaml -n openshift-migration