- Issued:
- 2021-03-15
- Updated:
- 2021-03-15
RHBA-2021:0814 - Bug Fix Advisory
Synopsis
Migration Toolkit for Containers (MTC) image release advisory 1.4.2
Type/Severity
Bug Fix Advisory
Topic
The Migration Toolkit for Containers (MTC) 1.4.2 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:
Solution
For more information about how to use this tool, see the following documentation:
Affected Products
- Red Hat Migration Toolkit 1 for RHEL 8 x86_64
- Red Hat Migration Toolkit 1 for RHEL 7 x86_64
Fixes
- BZ - 1913075 - Improve the wording and validation of exposed image registry route in UI
- BZ - 1916554 - Direct Volume Migration pods stuck at ContainerCreating status when PVC is in 'Terminating' state
- BZ - 1925065 - Direct Volume Migration stuck when Rsync pods fail because of OutOfCpu error
- BZ - 1925358 - Restic pod does not restart during IDVM migration from OCP 3.9
- BZ - 1925553 - Requesting MigAnalytic information from a "not ready" MigPlan breaks the analytic screen for all MigPlans
- BZ - 1926110 - Unable to log in to MTC console deployed on a cluster configured with a proxy
- BZ - 1926128 - Direct Volume Migration fails on a cluster configured with a proxy
- BZ - 1926774 - User still able to select DVM after selecting "Move" or "Snapshot" copy methods
- BZ - 1929806 - Direct Image Migration MigCluster validation fails on a cluster configured with a proxy
- BZ - 1934585 - MTC Operator icon is incorrect
- BZ - 1934666 - MigrationController pod crash-loops because of nil pointer exception
- BZ - 1936526 - "Exposed route host to image registry" field must be optional in the UI
- BZ - 1936549 - MTC version mismatch not reported in the MigPlan when the migration controller is deployed on the source cluster
- BZ - 1937295 - Upgrade from 1.3.2 to 1.4.2 fails because existing CRs are incompatible with new CRD schema
CVEs
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.