From fd8e235e92c8a1bb6b57023b7aae64b0df7465fa Mon Sep 17 00:00:00 2001 From: "A.Arnold" Date: Mon, 11 Aug 2025 11:56:16 +0100 Subject: [PATCH] MIG-1755: MTC 1.8.9 release notes Signed-off-by: A.Arnold --- .../release_notes/mtc-release-notes.adoc | 2 ++ .../migration-mtc-release-notes-1-8-9.adoc | 24 +++++++++++++++++++ 2 files changed, 26 insertions(+) create mode 100644 modules/migration-mtc-release-notes-1-8-9.adoc diff --git a/migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc b/migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc index 165937f5e8e9..ef2c63b75158 100644 --- a/migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc +++ b/migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc @@ -15,6 +15,8 @@ The {mtc-short} enables you to migrate application workloads between {product-ti For information on the support policy for {mtc-short}, see link:https://access.redhat.com/support/policy/updates/openshift#app_migration[OpenShift Application and Cluster Migration Solutions], part of the _Red Hat {product-title} Life Cycle Policy_. +include::modules/migration-mtc-release-notes-1-8-9.adoc[leveloffset=+1] + include::modules/migration-mtc-release-notes-1-8-8.adoc[leveloffset=+1] include::modules/migration-mtc-release-notes-1-8-7.adoc[leveloffset=+1] diff --git a/modules/migration-mtc-release-notes-1-8-9.adoc b/modules/migration-mtc-release-notes-1-8-9.adoc new file mode 100644 index 000000000000..3a527138a636 --- /dev/null +++ b/modules/migration-mtc-release-notes-1-8-9.adoc @@ -0,0 +1,24 @@ +// Module included in the following assemblies: +// +// * migration_toolkit_for_containers/mtc-release-notes-1-7.adoc + +:_mod-docs-content-type: REFERENCE +[id="migration-mtc-release-notes-1-8-9_{context}"] += {mtc-full} 1.8.9 release notes + +[id="resolved-issues-1-8-9_{context}"] +== Resolved issues + +{mtc-first} 1.8.9 has the following major resolved issues: + +.VM restarts migration after the MigPlan deletion + +Before this update, deleting the `MigPlan` triggered unnecessary virtual machine (VM) migrations. This caused the VMs to resume, leading to migration failures. This release introduces a fix that prevents VMs from migrating when the `MigPlan` is actively removed. As a result, VMs no longer unintentionally migrate when MigPlans are deleted, ensuring a stable environment for users. link:https://issues.redhat.com/browse/MIG-1749[(MIG-1749)] + +.Virt-launcher pod remain in pending after migrating the VM from hostpath-csi-basic to hostpath-csi-pvc-block + +Before this update, the `virt-launcher` pod stalled after migrating a VM due to pod anti-affinity conflicts with bound volumes. This resulted in a failed VM migration, causing the virt-launcher pod to get stuck. This release resolves the pod anti-affinity issue, allowing for scheduling on different nodes. As a result, you can now migrate VMs from `hostpath-csi-basic` to `hostpath-csi-pvc-block` without pods getting stuck in a pending state, thereby improving the overall migration process efficiency. link:https://issues.redhat.com/browse/MIG-1750[(MIG-1750)] + +.Migration-controller panics due to LimitRange "NIL" found in source project + +Before this update, the missing `Min` spec in a LimitRange within the `openshift-migration` namespace caused a panic in the migration-controller pod, disrupting the user experience and preventing successful volume migration. With this release, the migration-controller pod no longer crashes when encountering a LimitRange set to `Nil`. As a result, `rsync` pods now comply with the specified limits, improving the migration process stability and eliminating crashloopbacks in source namespaces.