RHEA-2020:0440 - Product Enhancement Advisory

Topic

The Red Hat Cluster Application Migration (CAM) Tool is now generally available.

Description

The Cluster Application Migration (CAM) tool 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 CAM web console or the Kubernetes API.

This advisory contains the images for the Cluster Application Migration tool. See the following advisory for metadata information:

https://access.redhat.com/errata/RHEA-2020:0441

Solution

For more information about how to use this tool, please see the following documentation:

https://docs.openshift.com/container-platform/4.3/migration/migrating-4_2-4/migrating-application-workloads-4_2-to-4.html

Affected Products

• Red Hat Migration Toolkit 1.1 x86_64

Fixes

• BZ - 1734492 - Failure in migration plan registry on the source cluster during cakephp-mysql app - NFS copy
• BZ - 1745906 - InitialBackupFailed when migrate app with imagestream from 3.9 to 4.2
• BZ - 1749831 - Migration of 50 (or above) projects fails with restic timeout.
• BZ - 1756408 - Warnings disappear while the migration is being executed
• BZ - 1756467 - Stage pod scheduling fails in clusters where pod affinity isn't working
• BZ - 1757212 - If the Destination Cluster for a migplan doesn't exist, the controller crashes with a nil pointer reference
• BZ - 1757571 - EnsureCloudSecretPropagated step hangs if src and dest clusters are both remote
• BZ - 1758269 - Inaccessible registered cluster blocks all attempts to close open migplans
• BZ - 1758336 - [MIG UI] Unable to edit namespace selection.
• BZ - 1760003 - [OCP42 - migration UI] mig-ui failed to show migration logs
• BZ - 1761702 - [CPMA]Not generated crio CR Manifest if souce cluster is using CRIO container
• BZ - 1762938 - [openshift-migration] CORS configuration for OCP4.1 and OCP4.2 should never be able to simultaneously configured
• BZ - 1768538 - Storage class not displayed when using beta annotation in the volume
• BZ - 1768667 - Creating a migplan with a dot in the name causes reconcile failure
• BZ - 1769535 - Cluster Migration Plan hung on EnsureCloudSecretPropagated
• BZ - 1770904 - Velero is not enabling incremental restore features
• BZ - 1772072 - Glusterblock RWO PV is not getting correct default storageclass
• BZ - 1772401 - [MIG-UI] Only the first migplan is deleted
• BZ - 1772936 - [MIG-UI] Wrong description in Azure blob credentials
• BZ - 1777658 - Only "Velero_Backups" resources group is allowed to execute an Azure snapshot migration
• BZ - 1777869 - [MIG-UI] Wrong storageclass name shown when creating a migration plan
• BZ - 1778896 - [MIG-UI] Wrong storageclass name shown when creating a migration plan
• BZ - 1778911 - The checkbox of Azure cluster is showing unchecked even it's checked while adding Azure cluster
• BZ - 1778915 - [MIG-UI] Sometimes PVs are not discovered
• BZ - 1778916 - [MIG-UI] Plans can be edited while running or closed
• BZ - 1781504 - cam-operator pulls operator image by tag instead of by digest
• BZ - 1783369 - Ceph warning shown when glusterfs move action is selected and no OCS4 installed
• BZ - 1784451 - Azure storage object not working
• BZ - 1789736 - [MIG-UI] Azure cluster information can not be edited
• BZ - 1790966 - [MIG-UI] Edit plan shows wrong information
• BZ - 1791310 - Migration fails if backup storage location's Spec.Config["insecureSkipTLSVerify"] is empty
• BZ - 1791323 - Velero pod crashes if ResticRepository.Status.LastMaintenanceTime is nil
• BZ - 1791379 - Show controller logs has occasional 404 error.
• BZ - 1792375 - Noobaa buckets with https are not working
• BZ - 1794128 - CAM should not allow users to `move` Azure volumes
• BZ - 1795729 - Migration Registry image location should be configurable

CVEs

(none)

References

(none)