RHEA-2021:2381 - Product Enhancement Advisory

Topic

Updated release packages that fix several bugs and add various enhancements are now available.

Description

Migration Toolkit for Virtualization 2.0.0 images

Solution

Before applying this update, make sure that all previously released errata relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Migration Toolkit for Virtualization 1 x86_64

Fixes

• BZ - 1884256 - If a source VM is inaccessible during migration, the migration plan displays an appropriate error message
• BZ - 1897065 - VMware VM name containing a slash ("/") marked as a critical concern by a Validation service rule
• BZ - 1897284 - Premigration check to ensure source VMs do not already exist on the target provider
• BZ - 1899362 - Web console displays '0' namespaces, VMs, and networks for target provider
• BZ - 1899371 - Add ability to cancel migration in web console
• BZ - 1900706 - Add support to cancel entire migration plan or VMs within a migration plan
• BZ - 1902028 - Validation stage with error messages added to the migration process
• BZ - 1902035 - MTV pod logs added to "must-gather" tool
• BZ - 1902487 - Migration plan custom resource with incorrect storage or network mapping succeeds
• BZ - 1902742 - Migration plan custom resource requires an initial validation to catch errors not caused by the VM Import Controller
• BZ - 1908020 - "Providers" link in the "Host details" page should point to the correct "Provider" tab
• BZ - 1908034 - "Host" page of VMware provider is missing information
• BZ - 1908745 - Add ability to get MTV version from the web console
• BZ - 1916958 - Migration plan status in web console does not switch from 'Critical' to 'Ready' after issue is fixed
• BZ - 1916960 - Web console does not display error message when target provider with incorrect URL is added
• BZ - 1923031 - VM name with upper-case letters passes validation (RFC-1123)
• BZ - 1927785 - Network mapping should be validated before migration
• BZ - 1928766 - Deleting a Provider custom resource does not delete the associated Host custom resources
• BZ - 1929050 - Add the ability to unset the migration network
• BZ - 1929731 - Target namespace auto-complete only matches the beginning of the namespace string
• BZ - 1934999 - Field name in VMware provider host configuration page is unclear
• BZ - 1940694 - Migration fails occasionally because the Virtual Machine Import custom resource is being updated
• BZ - 1940896 - Provider inventory changes not reflected in related custom resources
• BZ - 1941622 - Add link in web console to documentation
• BZ - 1942062 - After a provider is added in the web console, the focus should be on the new "Provider" tab
• BZ - 1942066 - Order of "Provider" tabs in web console should be consistent
• BZ - 1942080 - Improve text of the "Filter VMs" step of the Migration Plan wizard
• BZ - 1942091 - New namespaces created outside the web console are not picked up by polling
• BZ - 1942128 - Display data copied with greater precision by using decimal places to show MBs
• BZ - 1942135 - Breadcrumb hierarchy on Hosts page is confusing
• BZ - 1942137 - Add button to show/hide passwords and tokens
• BZ - 1942144 - Add a "required field" symbol to the "Name" field when saving network or storage mappings
• BZ - 1942259 - Provider validation status icons showed mismatch between severity and progress
• BZ - 1943355 - Provide restart option for cancelled migration plans
• BZ - 1944415 - Buttons and tooltips are confusing in the Create Mapping page
• BZ - 1945562 - VMs remain in "Analyzing" state in the "Migration Assessment" page of the Migration Plan wizard
• BZ - 1945567 - New network/storage mapping not saved when creating a migration plan
• BZ - 1946274 - Issues with status pipeline for warm migration
• BZ - 1947023 - Update API versions
• BZ - 1947519 - Clicking the 'Start' button does not start a migration plan immediately
• BZ - 1948965 - Destination storage in migration plan storage mapping is ignored. Default storage is picked instead.
• BZ - 1948975 - Migration network selection for hosts does not work
• BZ - 1950237 - Promote forklift.konveyor.io API to v1beta1
• BZ - 1951391 - Warm migration status in web console is 'Performing incremental data copy' after migration is cancelled
• BZ - 1951395 - Warm migration should fail early if CBT is not enabled on VMs
• BZ - 1952121 - Inventory container crashes because of OOM condition, causing controller pod restarts
• BZ - 1952312 - Replace VM ID with VM name in migration status message
• BZ - 1952362 - Status of first migrated VM is incomplete in Migration custom resource after successful migration
• BZ - 1952636 - Migration network selection list does not show the default migration network defined for the target provider
• BZ - 1953119 - Restarting a canceled warm migration plan shows incorrect status in the UI
• BZ - 1953307 - Entering incorrect credentials while selecting a migration network causes DDOS conditions for ESXi servers
• BZ - 1953938 - Text of migration concerns in VM selection page does not render line breaks ('\n')
• BZ - 1954228 - Update assessment text for snapshot validation rule
• BZ - 1954458 - CDI importer fails if the selected migration network for the target provider is not in the kube-system namespace
• BZ - 1956264 - Web console does not display precopy status when cutover is set in the Migration custom resource
• BZ - 1956268 - Web console displays a "Running cutover" migration plan status before the cutover time set in the Migration custom resource
• BZ - 1956467 - If a successfully migrated source VM is deleted, a new migration plan with different VMs fails because the scheduler is looking for the deleted VM
• BZ - 1956689 - Forklift Controller pod goes into CrashLoopbackOff state during installation
• BZ - 1957105 - Selecting a VM template for warm migration causes migration failure
• BZ - 1957877 - Restarted warm migration should behave like a new migration
• BZ - 1958649 - Mapping information disappears from "Plan summary" page if the plan is edited
• BZ - 1958652 - Default storage is used instead of the storage selected in the Migration Plan wizard
• BZ - 1958851 - Web console does not display a cutover that it is set in the Migration Plan custom resource
• BZ - 1959731 - Restarted cold migration plan shows already migrated VMs with "Transfer disks" status
• BZ - 1961891 - Incorrect status for migrated VMs during a warm migration retry
• BZ - 1962276 - VM inventory tree is slow to display if the source provider has more than 4000 VMs
• BZ - 1963285 - Migration analysis is stuck
• BZ - 1963880 - Forklift Controller pod restarts 4 times in 22 hours

CVEs

(none)

References

• null