RHEA-2021:2929 - Product Enhancement Advisory

Topic

The Migration Toolkit for Containers (MTC) 1.5.0 is now available.

Description

The Migration Toolkit for Containers (MTC) enables you to migrate
Kubernetes resources, persistent volume data, and internal container images
from an OpenShift Container Platform source cluster to an OpenShift
Container Platform target cluster, using the MTC web console or the
Kubernetes API.

This advisory contains the images for the Migration Toolkit for Containers.
See the following advisory for metadata information:

https://access.redhat.com/errata/RHBA-2021:76287

Solution

For more information about how to use MTC, see the following documentation:

https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html-single/migration_toolkit_for_containers/index

Affected Products

• Red Hat Migration Toolkit 1 for RHEL 8 x86_64
• Red Hat Migration Toolkit 1 for RHEL 7 x86_64

Fixes

• BZ - 1915279 - Pod health warning contains incorrect field name in the MigPlan CR status
• BZ - 1918971 - Remove hyperlink from the Location column on the Cluster page of the web console
• BZ - 1920455 - Migration status is "Succeeded" but the application did not migrate to GCP target cluster
• BZ - 1920559 - Rollback does not complete if the DVM Controller does not delete the Rsync pods
• BZ - 1922289 - Add hyperlink from Migration Plan warnings/errors to Migration Resources tree for debugging in web console
• BZ - 1929766 - Add Cluster window shows successful connection while Cluster page shows failed connection for new cluster
• BZ - 1929799 - Provide information about why an unavailable hook phase is not displayed in the Phase list on the Add Hook screen
• BZ - 1934877 - Add timeout parameters for the readiness and liveness probes of the Registry pod
• BZ - 1935633 - Data deleted in the Migration Controller CR was not deleted in the Migration Controller config map
• BZ - 1935674 - Warning from failed migration appears in migration plan "last stage" after issue is fixed
• BZ - 1943188 - "This migration is completed but progress information is not available" status appears briefly on the Migration Details page when migration starts
• BZ - 1945251 - Cluster remains in 'Critical' state after bad service account token is fixed
• BZ - 1948778 - Direct Volume Migration Progress pod does not record progress of Rsync pods accurately
• BZ - 1948780 - Direct Volume Migration Progress list of Rsync operations changes erratically in the web console
• BZ - 1949181 - 404 errors appear in Migration Resources tree in web console for cleaned up resources
• BZ - 1949459 - Web console crashes if 10+ migration plans are created and the browser is refreshed
• BZ - 1949518 - Last State column on the Migration Plans page does not automatically resize when it contains a long string
• BZ - 1951658 - Migration Resources tree does not identify the cluster of the resources
• BZ - 1955221 - Velero plugin uses S3 API version 2, which might not be supported by all S3 vendors
• BZ - 1957355 - No warning displayed when a migration plan containing deprecated APIs is run
• BZ - 1959724 - Namespaces page in web console displays duplicate "Plan total" rows when the migration plan contains multiple namespaces
• BZ - 1960289 - Rollback does not delete "Completed" deployment config Deployer and Hook pods, causing rollback to hang if PVCs are attached to the Hook pods
• BZ - 1960410 - Migration with "Verify" enabled in spec fails because the "v1beta1.Daemonset" extensions are not found on the target cluster
• BZ - 1966417 - Migration Resources tree on the Migration Details page in the web console is not updated
• BZ - 1966433 - 'PvUsageAnalysisFailed' error is displayed in MigPlan CR if source namespace is mapped to different target namespace
• BZ - 1966455 - Default storage class disappears from storage class list on Copy Options screen after namespace mapping is edited in migration plan
• BZ - 1966581 - Failed migration hook status is "Active" in the Migration Resources tree in the web console
• BZ - 1967161 - MigAnalytics returns incorrect data after namespace mapping is edited in MigPlan CR
• BZ - 1967499 - Incorrect error message is displayed in the web console when a namespace mapping is edited
• BZ - 1967580 - "Verify copy" column name is truncated on "Copy options" page of web console
• BZ - 1967764 - Resources not restored when migrating from OpenShift Container Platform 3.11 to 4.3
• BZ - 1967858 - Custom resources are not migrated
• BZ - 1970102 - Update 'mig-log-reader' filters to reduce noise caused by Velero 1.6 log strings
• BZ - 1972284 - Attempts to run different migration plans in the web console result in running the same migration plan
• BZ - 1972903 - No error reported when target namespace creation fails during direct volume migration
• BZ - 1974497 - Migration Phase selection field on Add Hook window does not work
• BZ - 1975239 - Adding an existing hook in the Add Hook window and then clicking "Cancel" disables the Add Hook fields when adding a new hook
• BZ - 1975370 - Web console does not validate the length of a mapped target namespace in a migration plan
• BZ - 1975485 - "View debug page for more info" hyperlink on the Migration Plans page does not point directly to the Migration Resources tree
• BZ - 1975863 - Web console crashes if migration plan status is "not ready"
• BZ - 1976048 - "oc log" command with "--selector" does not print all the specified logs
• BZ - 1978561 - MigMigration CR with "spec.verify=true" fails with apiVersion error
• BZ - 1981335 - MTC cannot be deployed on OpenShift Container Platform version 3.10
• BZ - 1981649 - MTC cannot be deployed on OpenShift Container Platform version 3.9

CVEs

(none)

References

(none)