update

anarnold97 · anarnold97 · commit 6fc839b5a276 · 2025-08-11T13:09:18.000+01:00
Signed-off-by: A.Arnold &lt;anarnold@redhat.com&gt;
diff --git a/modules/migration-mtc-release-notes-1-8-9.adoc b/modules/migration-mtc-release-notes-1-8-9.adoc
@@ -21,4 +21,4 @@ Before this update, the `virt-launcher` pod stalled after migrating a VM due to
 
 .Migration-controller Panic 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. link:https://issues.redhat.com/browse/MIG-1731[(MIG-1731)]
+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.

Original file line number	Diff line number	Diff line change
@@ -21,4 +21,4 @@ Before this update, the `virt-launcher` pod stalled after migrating a VM due to
`21`	`21`
`22`	`22`	`.Migration-controller Panic due to LimitRange "NIL" found in source project`
`23`	`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. link:https://issues.redhat.com/browse/MIG-1731[(MIG-1731)]
	`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.