Chapter 7. Upgrading the Migration Toolkit for Virtualization

You can upgrade the MTV Operator by using the OpenShift Container Platform web console to install the new version.

Note

You must upgrade to the next release without skipping a release, for example, from 2.0 to 2.1 or from 2.1 to 2.2.

Procedure

  1. In the OCP web console, click Operators → Installed Operators → Migration Tookit for Virtualization Operator → Subscription.

  2. Change the update channel to the correct release.

    See Changing update channel in the OpenShift Container Platform documentation.

  3. Confirm that Upgrade status changes from Up to date to Upgrade available. If it does not, restart the CatalogSource pod:

    1. Note the catalog source, for example, redhat-operators.

    2. From the command line, retrieve the catalog source pod: 

      $ oc get pod -n openshift-marketplace | grep <catalog_source>

    3. Delete the pod: 

      $ oc delete pod -n openshift-marketplace <catalog_source_pod>

      Upgrade status changes from Up to date to Upgrade available.

      If you set Update approval on the Subscriptions tab to Automatic, the upgrade starts automatically.

  4. If you set Update approval on the Subscriptions tab to Manual, approve the upgrade.

    See Manually approving a pending upgrade in the OpenShift Container Platform documentation.

  5. Verify that the forklift-ui pod is in a Ready state before you log in to the web console: 

    $ oc get pods -n openshift-mtv

    Example output

    NAME                                  READY  STATUS   RESTARTS  AGE
forklift-controller-788bdb4c69-mw268  2/2    Running  0         2m
forklift-operator-6bf45b8d8-qps9v     1/1    Running  0         5m
forklift-ui-7cdf96d8f6-xnw5n          1/1    Running  0         2m

  6. If you added VMware source providers to MTV 2.2, upgrading to MTV 2.3 changes the state of any VMware providers to Critical. To fix this problem, edit the VMwhere provider by adding a VDDK init image and verifying the certificate of the VMware provider. For more information see Addding a VMSphere source provider.
  7. If you mapped to NFS on the OpenShift Container Platform destination provider in MTV 2.2, upgrading to MTV 2.3 invalidates the NFS mapping. To fix this problem, edit the AccessModes and VolumeMode parameters in the NFS storage profile. For more information, see Customizing the storage profile.