Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Release notes
Version 2.1
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Migration Toolkit for Virtualization 2.1
You can migrate virtual machines (VMs) from VMware vSphere or Red Hat Virtualization to OpenShift Virtualization with the Migration Toolkit for Virtualization (MTV).
The release notes describe new features and enhancements, known issues, and technical changes.
1.1. Technical changes
VDDK image added to HyperConverged custom resource
The VMware Virtual Disk Development Kit (VDDK) SDK image must be added to the HyperConverged custom resource. Before this release, it was referenced in the v2v-vmware config map.
1.2. New features and enhancements
This release adds the following features and improvements.
Cold migration from Red Hat Virtualization
You can perform a cold migration of VMs from Red Hat Virtualization.
Migration hooks
You can create migration hooks to run Ansible playbooks or custom code before or after migration.
Filtered must-gather data collection
You can specify options for the must-gather tool that enable you to filter the data by namespace, migration plan, or VMs.
SR-IOV network support
You can migrate VMs with a single root I/O virtualization (SR-IOV) network interface if the OpenShift Virtualization environment has an SR-IOV network.
1.3. Known issues
QEMU guest agent is not installed on migrated VMs
The QEMU guest agent is not installed on migrated VMs. Workaround: Install the QEMU guest agent with a post-migration hook. (BZ#2018062)
Disk copy stage does not progress
The disk copy stage of a RHV VM does not progress and the MTV web console does not display an error message. (BZ#1990596)
The cause of this problem might be one of the following conditions:
- The storage class does not exist on the target cluster.
-
The VDDK image has not been added to the
HyperConvergedcustom resource. - The VM does not have a disk.
- The VM disk is locked.
- The VM time zone is not set to UTC.
- The VM is configured for a USB device.
To disable USB devices, see Configuring USB Devices in the Red Hat Virtualization documentation.
To determine the cause:
- Click Workloads → Virtualization in the OpenShift Container Platform web console.
- Click the Virtual Machines tab.
- Select a virtual machine to open the Virtual Machine Overview screen.
- Click Status to view the status of the virtual machine.
VM time zone must be UTC with no offset
The time zone of the source VMs must be UTC with no offset. You can set the time zone to GMT Standard Time after first assessing the potential impact on the workload. (BZ#1993259)
RHV resource UUID causes a "Provider not found" error
If a RHV resource UUID is used in a Host, NetworkMap, StorageMap, or Plan custom resource (CR), a "Provider not found" error is displayed.
You must use the resource name. (BZ#1994037)
Same RHV resource name in different data centers causes ambiguous reference
If a RHV resource name is used in a NetworkMap, StorageMap, or Plan custom resource (CR) and if the same resource name exists in another data center, the Plan CR displays a critical "Ambiguous reference" condition. You must rename the resource or use the resource UUID in the CR.
In the web console, the resource name appears twice in the same list without a data center reference to distinguish them. You must rename the resource. (BZ#1993089)
Snapshots are not deleted after warm migration
Snapshots are not deleted automatically after a successful warm migration of a VMware VM. You must delete the snapshots manually in VMware vSphere. (BZ#2001270)
Chapter 2. Migration Toolkit for Virtualization 2.0
You can migrate virtual machines (VMs) from VMware vSphere to OpenShift Virtualization with the Migration Toolkit for Virtualization (MTV).
The release notes describe new features and enhancements, known issues, and technical changes.
2.1. New features and enhancements
This release adds the following features and improvements.
Warm migration
Warm migration reduces downtime by copying most of the VM data during a precopy stage while the VMs are running. During the cutover stage, the VMs are stopped and the rest of the data is copied.
Cancel migration
You can cancel an entire migration plan or individual VMs while a migration is in progress. A canceled migration plan can be restarted in order to migrate the remaining VMs.
Migration network
You can select a migration network for the source and target providers for improved performance. By default, data is copied using the VMware administration network and the OpenShift Container Platform pod network.
Validation service
The validation service checks source VMs for issues that might affect migration and flags the VMs with concerns in the migration plan.
The validation service is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/.
2.2. Known issues
This section describes known issues and mitigations.
QEMU guest agent is not installed on migrated VMs
The QEMU guest agent is not installed on migrated VMs. Workaround: Install the QEMU guest agent with a post-migration hook. (BZ#2018062)
Network map displays a "Destination network not found" error
If the network map remains in a NotReady state and the NetworkMap CR manifest displays a Destination network not found error, the cause is a missing network attachment definition. You must create a network attachment definition for each additional destination network before you create the network map. (BZ#1971259)
Warm migration gets stuck during third precopy
Warm migration uses changed block tracking snapshots to copy data during the precopy stage. The snapshots are created at one-hour intervals by default. When a snapshot is created, its contents are copied to the destination cluster. However, when the third snapshot is created, the first snapshot is deleted and the block tracking is lost. (BZ#1969894)
You can do one of the following to mitigate this issue:
- Start the cutover stage no more than one hour after the precopy stage begins so that only one internal snapshot is created.
Increase the snapshot interval in the
vm-import-controller-configconfig map to720minutes:$ oc patch configmap/vm-import-controller-config \ -n openshift-cnv -p '{"data": \ {"warmImport.intervalMinutes": "720"}}'
