Review the resolved issues in this release of {project-short}.
- User could not rename virtual machines to address naming conflicts before migration
-
In previous versions of {project-short}, you could not rename virtual machines (VMs) from the source provider to address naming conflicts before the VMs were migrated to Red Hat {virt}. In this release of {project-short}, you can modify non-compliant VM names in the {project-short} UI during the migration process to address naming conflicts and ensure compatibility with {virt} naming conventions. (MTV-2919)
- User experience was interrupted when adding a new target project to a migration plan
-
In previous versions of {project-short}, you had to close the Create migration plan wizard in the MTV UI to add a new target project to your migration plan. In this release of {project-short}, the option to create a new project as a target for VMs in your migration plan is available in the Target project dropdown list on the General page of the Create migration plan wizard.
- Power state of source VMs was preserved post-migration
-
In previous versions of {project-short}, the power state of a source VM was preserved post-migration. In this release of {project-short}, you can set the power state of a migrated VM to
on,off, orauto. For example, if you are migrating a VM that is running in the source environment, you can ensure that the VM is powered off post-migration to preserve startup dependencies between VMs. With this update, you can set the power state for the target VM in the MTV UI or by using thepowerStatefield in thespec.vmssection of thePlanCustom Resource (CR). Theautosetting preserves the power state of the source VM. (MTV-1312)