Skip to content

Commit d9a8b1e

Browse files
authored
Merge pull request #97591 from openshift-cherrypick-robot/cherry-pick-97371-to-enterprise-4.16
[enterprise-4.16] MIG-1755: MTC 1.8.9 release notes
2 parents 270fd7a + 7188233 commit d9a8b1e

File tree

2 files changed

+26
-0
lines changed

2 files changed

+26
-0
lines changed

migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,8 @@ The {mtc-short} enables you to migrate application workloads between {product-ti
1515

1616
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_.
1717

18+
include::modules/migration-mtc-release-notes-1-8-9.adoc[leveloffset=+1]
19+
1820
include::modules/migration-mtc-release-notes-1-8-8.adoc[leveloffset=+1]
1921

2022
include::modules/migration-mtc-release-notes-1-8-7.adoc[leveloffset=+1]
Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * migration_toolkit_for_containers/mtc-release-notes-1-7.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="migration-mtc-release-notes-1-8-9_{context}"]
7+
= {mtc-full} 1.8.9 release notes
8+
9+
[id="resolved-issues-1-8-9_{context}"]
10+
== Resolved issues
11+
12+
{mtc-first} 1.8.9 has the following major resolved issues:
13+
14+
.VM restarts migration after the MigPlan deletion
15+
16+
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)]
17+
18+
.Virt-launcher pod remain in pending after migrating the VM from hostpath-csi-basic to hostpath-csi-pvc-block
19+
20+
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)]
21+
22+
.Migration-controller panics due to LimitRange "NIL" found in source project
23+
24+
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.

0 commit comments

Comments
 (0)