Repository: openshift/openshift-docs
Pull request #91067: MIG-1687: Release notes for MTC 1.8.6
Author: login: anarnold97
Labels: name: peer-review-done
description: Signifies that the peer review team has reviewed this PR
name: size/M
description: Denotes a PR that changes 30-99 lines, ignoring generated files.
name: MTC
description: Label for all MTC PRs
name: jira/valid-reference
description: Indicates that this PR references a valid Jira ticket of any type.
name: branch/enterprise-4.13
name: branch/enterprise-4.14
name: branch/enterprise-4.15
name: branch/enterprise-4.16
name: branch/enterprise-4.17
name: branch/enterprise-4.18
name: branch/enterprise-4.19
Created: 2025-03-25T15:57:26Z | Merged: 2025-04-22T20:25:37Z

### JIRA

* [MIG-1687](https://issues.redhat.com/browse/MIG-1687)


### Version(s):

* OCP 4.13 → branch/enterprise-4.13
* OCP 4.14 → branch/enterprise-4.14
* OCP 4.15 → branch/enterprise-4.15
* OCP 4.16 → branch/enterprise-4.16
* OCP 4.17 → branch/enterprise-4.17
* OCP 4.18 → branch/enterprise-4.18
* OCP 4.19 → branch/enterprise-4.19

### Link to docs preview:

* [MTC 1.8.6 release notes](https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html#migration-mtc-release-notes-1-8-6_mtc-release-notes)

### QE review:
- [ ] QE has approved this change.
<!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->

Additional information:
<!--- Optional: Include additional context or expand the description here.--->

<!--- After you open your PR, ask for review from the OpenShift docs team:
  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->



Diff:
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 e015e8feac43..8de3d31131cc 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,7 @@ 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-6.adoc[leveloffset=+1]
 include::modules/migration-mtc-release-notes-1-8-5.adoc[leveloffset=+1]
 include::modules/migration-mtc-release-notes-1-8-4.adoc[leveloffset=+1]
 include::modules/migration-mtc-release-notes-1-8-3.adoc[leveloffset=+1]
diff --git a/modules/migration-mtc-release-notes-1-8-6.adoc b/modules/migration-mtc-release-notes-1-8-6.adoc
new file mode 100644
index 000000000000..4da835875386
--- /dev/null
+++ b/modules/migration-mtc-release-notes-1-8-6.adoc
@@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes fails to complete after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes fails to complete after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without persistent volume claims
+When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page remains indefinitely with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. 
+
+This issue is not only limited to unusual or unexpected cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 


Reviews:
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-26T10:43:48Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-03-26T10:45:44Z
user: login: ocpdocs-vale-bot
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-03-26T10:59:54Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-05T12:11:28Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-05T12:16:33Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-05T12:18:00Z
user: login: rayfordj
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-16T14:07:55Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T14:18:18Z
user: login: midays
state: CHANGES_REQUESTED
author_association: NONE
submitted_at: 2025-04-16T14:22:15Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T15:47:39Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-16T15:48:28Z
user: login: midays
body: it doesn't only happen in the edge case, when migration is done with network restriction applied ( so the dvm should fail ) theUI shows wron status as well
state: CHANGES_REQUESTED
author_association: NONE
submitted_at: 2025-04-17T08:47:08Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T09:24:02Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T09:24:49Z
user: login: midays
state: CHANGES_REQUESTED
author_association: NONE
submitted_at: 2025-04-17T10:52:46Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T12:00:03Z
user: login: midays
body: LGTM
state: APPROVED
author_association: NONE
submitted_at: 2025-04-17T12:03:05Z
user: login: lpettyjo
body: Otherwise, LGTM! Nice work!
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:29:41Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:33:18Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:34:12Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:36:14Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:36:38Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:37:37Z
user: login: anarnold97
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-17T17:40:43Z

Review comments:
diff_hunk: @@ -0,0 +1,41 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.4 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
[id="new-features-1-8-6_{context}"]
== New features
```
created_at: 2025-03-26T10:43:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,41 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.4 release notes
+
+[id="new-features-1-8-6_{context}"]
+== New features
+
+
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.Multiple migration plans for a namespace

Before the release of {mtc-short} 1.8.6, you were unable to have more than one migration plan for a namespace.  If another migration plan attempted to use a namespace that was associated with another migration plan, the plan would be rejected. 

In {mtc-short} 1.8.6, you can have multiple migration plans associated with the same namespace, provided that your migration plans do not reference the same persistent volumes (PVs). 

By having multiple migration plans associated with the same namespace, you can design different migration plans for applications that reside in the same namespace.
```
created_at: 2025-03-26T10:45:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,47 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.4 release notes
+
+[id="new-features-1-8-6_{context}"]
+== New features
+
+.Multiple migration plans for a namespace
+
+Before the release of {mtc-short} 1.8.6, you were unable to have more than one migration plan for a namespace.  If another migration plan attempted to use a namespace that was associated with another migration plan, the plan would be rejected. 
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: ocpdocs-vale-bot
body: 🤖 **[error] RedHat.Spacing**: Keep one space between words in 'namespace.  If'. For more information, see [RedHat.Spacing](https://redhat-documentation.github.io/vale-at-red-hat/docs/main/reference-guide/spacing).
created_at: 2025-03-26T10:59:54Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,46 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="new-features-1-8-6_{context}"]
+== New features
+
+.Multiple migration plans for a namespace
+
+Before the release of {mtc-short} 1.8.6, you were unable to have more than one migration plan for a namespace. If another migration plan attempted to use a namespace that was associated with another migration plan, the plan was rejected. 
+
+In {mtc-short} 1.8.6, you can have more than one migration plans associated with the same namespace, if your migration plans do not reference the same persistent volumes (PVs). 
+
+By having more than one migration plan associated with the same namespace, you can design different migration plans for applications that are in the same namespace.
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.Migration shown as succeeded despite a failed phase due to a misleading UI status

After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
```
created_at: 2025-04-05T12:11:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,48 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="new-features-1-8-6_{context}"]
+== New features
+
+.Multiple migration plans for a namespace
+
+Before the release of {mtc-short} 1.8.6, you were unable to have more than one migration plan for a namespace. If another migration plan attempted to use a namespace that was associated with another migration plan, the plan was rejected. 
+
+In {mtc-short} 1.8.6, you can have more than one migration plans associated with the same namespace, if your migration plans do not reference the same persistent volumes (PVs). 
+
+By having more than one migration plan associated with the same namespace, you can design different migration plans for applications that are in the same namespace.
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in migration plan wizard
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.UI crashes during a namespace search in the migration plan wizard
```
created_at: 2025-04-05T12:16:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,48 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="new-features-1-8-6_{context}"]
+== New features
+
+.Multiple migration plans for a namespace
+
+Before the release of {mtc-short} 1.8.6, you were unable to have more than one migration plan for a namespace. If another migration plan attempted to use a namespace that was associated with another migration plan, the plan was rejected. 
+
+In {mtc-short} 1.8.6, you can have more than one migration plans associated with the same namespace, if your migration plans do not reference the same persistent volumes (PVs). 
+
+By having more than one migration plan associated with the same namespace, you can design different migration plans for applications that are in the same namespace.
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion

.Migration shown as succeeded despite a failed phase due to a misleading UI status
```
created_at: 2025-04-05T12:18:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes status from Technical Preview status to being generally available.
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: rayfordj
body: ```suggestion
VM storage migration feature changes from Technical Preview status to being Generally Available.
```
Should "Generally Available" here be capitalized similar to "Technical Preview"?
Remove one of the use of 'status' here?
created_at: 2025-04-16T14:07:55Z
author_association: NONE
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technical Preview status to being Generally Available.
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
```
created_at: 2025-04-16T14:18:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: midays
body: we need to document the [MIG-1719](https://issues.redhat.com/browse/MIG-1719) issue
created_at: 2025-04-16T14:21:55Z
author_association: NONE
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion

.Inconsistent reporting of migration failure status

There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]
```
created_at: 2025-04-16T15:47:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]
+////
+.The associated SCC for service account cannot be migrated in {OCP} 4.12
+
+The associated Security Context Constraints (SCCs) for service accounts in {OCP} 4.12 cannot be migrated. This issue is planned to be resolved in a future release of {mtc-short}. link:https://issues.redhat.com/browse/MIG-1454[(MIG-1454)].
+////
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion

```
created_at: 2025-04-16T15:48:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,47 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: midays
body: ```suggestion
There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]

Additionally, this issue is not limited to edge cases. In certain scenarios—such as when network restrictions are applied that cause the DVM phase to fail—the UI still reports the migration status as succeeded. This behavior is similar to what was previously observed in MIG-1711 but occurs under different conditions.
```
created_at: 2025-04-17T08:46:20Z
author_association: NONE
diff_hunk: @@ -0,0 +1,47 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
```
created_at: 2025-04-17T09:24:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,47 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. 

This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
```
created_at: 2025-04-17T09:24:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: midays
body: we also jave ave this bug that was recently verified:
https://issues.redhat.com/browse/MIG-1713
created_at: 2025-04-17T10:52:38Z
author_association: NONE
diff_hunk: @@ -0,0 +1,49 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion

.Persistent Volumes page hangs indefinitely for namespaces without PVCs
When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page becomes stuck with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]

```
created_at: 2025-04-17T12:00:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: Try to use a more descriptive term for "crash", such as "fails" or "ends unexpectedly". IBM SG.
created_at: 2025-04-17T17:18:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: Same comment as above.
created_at: 2025-04-17T17:19:00Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: ```suggestion
In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
```
created_at: 2025-04-17T17:21:15Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: Same comment as above.
created_at: 2025-04-17T17:22:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without PVCs
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: ```suggestion
.Persistent Volumes page remains indefinitely for namespaces without PVCs
```
Same comment as above.
created_at: 2025-04-17T17:23:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without PVCs
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: The acronym PVC is not spelled out here, but is below. Not sure what the convention is here. Do you spell out on first instance for the topic, or for each bug?
created_at: 2025-04-17T17:25:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without PVCs
+When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page becomes stuck with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: ```suggestion
When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page remains indefinitely with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]
```
created_at: 2025-04-17T17:26:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+When creating a migration plan in {mtc-short}, the UI becomes stuck on the *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without PVCs
+When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page becomes stuck with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. 
+
+This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: lpettyjo
body: Not sure about using the term "edge case". Not everyone will know what that means and it will translate poorly. Perhaps "unusual cases"?
created_at: 2025-04-17T17:29:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI crashes during a namespace search in the migration plan wizard
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.UI fails during a namespace search in the migration plan wizard
```
created_at: 2025-04-17T17:33:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) crashes and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
```
created_at: 2025-04-17T17:34:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes stuck after the `StageBackup` phase
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.Migration process becomes fails to complete after the `StageBackup` phase
```
created_at: 2025-04-17T17:36:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes fails to complete after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes stuck after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
When migrating a Django and PostgreSQL application, the migration becomes fails to complete after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
```
created_at: 2025-04-17T17:36:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes fails to complete after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes fails to complete after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without PVCs
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
.Persistent Volumes page hangs indefinitely for namespaces without persistent volume claims
```
created_at: 2025-04-17T17:37:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,52 @@
+// Module included in the following assemblies:
+//
+// * migration_toolkit_for_containers/mtc-release-notes.adoc
+:_mod-docs-content-type: REFERENCE
+[id="migration-mtc-release-notes-1-8-6_{context}"]
+= {mtc-full} 1.8.6 release notes
+
+[id="technical-changes-1-8-6_{context}"]
+== Technical changes
+
+.Multiple migration plans for a namespace is not supported
+
+{mtc-short} version 1.8.6 and later do not support multiple migration plans for a single namespace.
+
+.VM storage migration
+
+VM storage migration feature changes from Technology Preview (TP) status to being Generally Available (GA).
+
+[id="resolved-issues-1-8-6_{context}"]
+== Resolved issues
+
+{mtc-short} 1.8.6 has the following major resolved issues:
+
+.UI fails during a namespace search in the migration plan wizard
+
+When searching for a namespace in the *Select Namespace* step of the migration plan wizard, the user interface (UI) fails and disappears after clicking *Search*. The browser console shows a JavaScript error indicating that an undefined value has been accessed. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1704[(MIG-1704)]
+
+.Unable to create a migration plan due to a reconciliation failure
+
+In {mtc-short}, when creating a migration plan , the UI remains on *Persistent Volumes* and you cannot continue. This issue occurs due to a critical reconciliation failure and returns a 404 API error when you attempt to fetch the migration plan from the backend. These issues cause the migration plan to remain in a *Not Ready* state, and you are prevented from continuing. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1705[(MIG-1705)]
+
+.Migration process becomes fails to complete after the `StageBackup` phase
+
+When migrating a Django and PostgreSQL application, the migration becomes fails to complete after the `StageBackup` phase. Even though all the pods in the source namespace are healthy before the migration begins, after the migration and when terminating the pods on the source cluster, the Django pod fails with a `CrashLoopBackOff` error. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1707[(MIG-1707)]
+
+.Migration shown as succeeded despite a failed phase due to a misleading UI status
+
+After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
+
+.Persistent Volumes page hangs indefinitely for namespaces without persistent volume claims
+When a migration plan includes a namespace that does not have any persistent volume claims (PVCs), the *Persistent Volumes* selection page remains indefinitely with the following message shown: `Discovering persistent volumes attached to source projects...`. The page never completes loading, preventing you from proceeding with the migration. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1713[(MIG-1713)]
+
+[id="known-issues-1-8-6_{context}"]
+== Known issues
+
+{mtc-short} 1.8.6 has the following known issues:
+
+.Inconsistent reporting of migration failure status
+
+There is a discrepancy in the reporting of namespace migration status following a rollback and subsequent re-migration attempt when the migration plan is deliberately faulted. Although the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface (UI) or the migration plan's YAML representation. 
+
+This issue is not only limited to edge cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
path: modules/migration-mtc-release-notes-1-8-6.adoc
user: login: anarnold97
body: ```suggestion
This issue is not only limited to unusual or unexpected cases. In certain circumstances, such as when network restrictions are applied that cause the DVM phase to fail, the UI still reports the migration status as successful. This behavior is similar to what was previously observed in link:https://issues.redhat.com/browse/MIG-1711[MIG-1711] but occurs under different conditions. link:https://issues.redhat.com/browse/MIG-1719[(MIG-1719)] 
```
created_at: 2025-04-17T17:40:43Z
author_association: CONTRIBUTOR

PR comments:
user: login: openshift-ci-robot
created_at: 2025-03-25T15:57:32Z
body: @anarnold97: This pull request references [MIG-1687](https://issues.redhat.com//browse/MIG-1687) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067):

>### JIRA
>
>* [MIG-1687](https://issues.redhat.com/browse/MIG-1687)
>
><!--- If your changes apply to the latest release and/or in-development version of OpenShift, open your PR against the `main` branch.
>Do not create or rename a top-level directory (or any subdirectory in a directory that contains a hugebook.flag file) in the repository and topic map without checking with a docs program manager first.
>If a book is being created or modified, there are changes on the Customer Portal that must also be made.
>
>* For more details about the information requested in this template, see:
>  https://github.com/openshift/openshift-docs/blob/main/contributing_to_docs/create_or_edit_content.adoc#submit-PR --->
>
>Version(s):
><!--- Specify the version or versions of OpenShift your PR applies to. -->
>
>Issue:
><!--- Add a link to the Bugzilla, Jira, or GitHub issue, if applicable. --->
>
>Link to docs preview:
><!--- Add direct link(s) to the exact page(s) with updated content from the preview build. --->
>
>QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: ocpdocs-previewbot
created_at: 2025-03-25T16:05:31Z
body: 🤖 Thu Apr 17 17:57:40 - Prow CI generated the docs preview:

https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-05T12:21:08Z
body: @anarnold97: This pull request references [MIG-1687](https://issues.redhat.com//browse/MIG-1687) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067):

>### JIRA
>
>* [MIG-1687](https://issues.redhat.com/browse/MIG-1687)
>
>
>### Version(s):
>
>* OCP 4.13 → branch/enterprise-4.13
>* OCP 4.14 → branch/enterprise-4.14
>* OCP 4.15 → branch/enterprise-4.15
>* OCP 4.16 → branch/enterprise-4.16
>* OCP 4.17 → branch/enterprise-4.17
>* OCP 4.18 → branch/enterprise-4.18
>* OCP 4.19 → branch/enterprise-4.19
>
>### Link to docs preview:
>
>* [MTC 1.8.6](https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html#migration-mtc-release-notes-1-8-6_mtc-release-notes)
>
>### QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-05T12:28:26Z
body: @anarnold97: This pull request references [MIG-1687](https://issues.redhat.com//browse/MIG-1687) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067):

>### JIRA
>
>* [MIG-1687](https://issues.redhat.com/browse/MIG-1687)
>
>
>### Version(s):
>
>* OCP 4.13 → branch/enterprise-4.13
>* OCP 4.14 → branch/enterprise-4.14
>* OCP 4.15 → branch/enterprise-4.15
>* OCP 4.16 → branch/enterprise-4.16
>* OCP 4.17 → branch/enterprise-4.17
>* OCP 4.18 → branch/enterprise-4.18
>* OCP 4.19 → branch/enterprise-4.19
>
>### Link to docs preview:
>
>* [MTC 1.8.6 release notes](https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html#migration-mtc-release-notes-1-8-6_mtc-release-notes)
>
>### QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: anarnold97
created_at: 2025-04-16T15:49:46Z
body: @midays & @rayfordj - updated, please re-review
Thanks
author_association: CONTRIBUTOR
user: login: rayfordj
created_at: 2025-04-16T15:58:46Z
body: /lgtm
author_association: NONE
user: login: rayfordj
created_at: 2025-04-16T15:59:50Z
body: /unassign @rayfordj 
author_association: NONE
user: login: openshift-ci-robot
created_at: 2025-04-16T18:56:57Z
body: @anarnold97: This pull request references [MIG-1687](https://issues.redhat.com//browse/MIG-1687) which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067):

>### JIRA
>
>* [MIG-1687](https://issues.redhat.com/browse/MIG-1687)
>
>
>### Version(s):
>
>* OCP 4.13 → branch/enterprise-4.13
>* OCP 4.14 → branch/enterprise-4.14
>* OCP 4.15 → branch/enterprise-4.15
>* OCP 4.16 → branch/enterprise-4.16
>* OCP 4.17 → branch/enterprise-4.17
>* OCP 4.18 → branch/enterprise-4.18
>* OCP 4.19 → branch/enterprise-4.19
>
>### Link to docs preview:
>
>* [MTC 1.8.6 release notes](https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html#migration-mtc-release-notes-1-8-6_mtc-release-notes)
>
>### QE review:
>- [ ] QE has approved this change.
><!--- QE approval is required to merge a PR except for changes that do not impact the meaning of the docs. --->
>
>Additional information:
><!--- Optional: Include additional context or expand the description here.--->
>
><!--- After you open your PR, ask for review from the OpenShift docs team:
>  For community authors: Tag @openshift/team-documentation in a GitHub comment.--->
>


Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fopenshift-docs).  If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
</details>
author_association: NONE
user: login: anarnold97
created_at: 2025-04-16T19:48:01Z
body: /label mtc
author_association: CONTRIBUTOR
user: login: rayfordj
created_at: 2025-04-16T19:59:00Z
body: /lgtm
author_association: NONE
user: login: rayfordj
created_at: 2025-04-16T19:59:13Z
body: /unassign @rayfordj 
author_association: NONE
user: login: anarnold97
created_at: 2025-04-16T20:01:17Z
body: @midays - down to your review, which i need for a merge review
thanks
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-04-17T09:24:23Z
body: New changes are detected. LGTM label has been removed.
author_association: NONE
user: login: anarnold97
created_at: 2025-04-17T13:31:40Z
body: /label peer-review-needed
author_association: CONTRIBUTOR
user: login: anarnold97
created_at: 2025-04-17T17:50:26Z
body: @lpettyjo - thanks
author_association: CONTRIBUTOR
user: login: openshift-ci[bot]
created_at: 2025-04-17T17:58:28Z
body: @anarnold97: all tests **passed!**


[Full PR test history](https://prow.ci.openshift.org/pr-history?org=openshift&repo=openshift-docs&pr=91067). [Your PR dashboard](https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:anarnold97).

<details>

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
</details>
<!-- test report -->
author_association: NONE
user: login: anarnold97
created_at: 2025-04-22T11:14:52Z
body: /label merge-review-needed
author_association: CONTRIBUTOR
user: login: jab-rh
created_at: 2025-04-22T20:25:43Z
body: /cherry-pick enterprise-4.19
author_association: CONTRIBUTOR
user: login: jab-rh
created_at: 2025-04-22T20:25:51Z
body: /cherry-pick enterprise-4.18
author_association: CONTRIBUTOR
user: login: jab-rh
created_at: 2025-04-22T20:26:08Z
body: /cherry-pick enterprise-4.17
author_association: CONTRIBUTOR
user: login: jab-rh
created_at: 2025-04-22T20:26:20Z
body: /cherry-pick enterprise-4.16
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:26:32Z
body: @jab-rh: new pull request created: #92497

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822398530):

>/cherry-pick enterprise-4.19


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: jab-rh
created_at: 2025-04-22T20:26:36Z
body: /cherry-pick enterprise-4.15
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:26:40Z
body: @jab-rh: new pull request created: #92498

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822398920):

>/cherry-pick enterprise-4.18


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: jab-rh
created_at: 2025-04-22T20:26:51Z
body: /cherry-pick enterprise-4.14
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:26:58Z
body: @jab-rh: new pull request created: #92499

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822399798):

>/cherry-pick enterprise-4.17


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: jab-rh
created_at: 2025-04-22T20:27:02Z
body: /cherry-pick enterprise-4.13
author_association: CONTRIBUTOR
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:27:08Z
body: @jab-rh: new pull request created: #92500

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822400745):

>/cherry-pick enterprise-4.16


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:27:27Z
body: @jab-rh: new pull request created: #92501

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822401660):

>/cherry-pick enterprise-4.15


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:27:38Z
body: @jab-rh: new pull request created: #92502

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822402558):

>/cherry-pick enterprise-4.14


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: openshift-cherrypick-robot
created_at: 2025-04-22T20:27:47Z
body: @jab-rh: #91067 failed to apply on top of branch "enterprise-4.13":
```
Applying: WIP - MIG-1687: Release notes for MTC 1.8.6
.git/rebase-apply/patch:62: trailing whitespace.
After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc
CONFLICT (content): Merge conflict in migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 WIP - MIG-1687: Release notes for MTC 1.8.6

```

<details>

In response to [this](https://github.com/openshift/openshift-docs/pull/91067#issuecomment-2822403178):

>/cherry-pick enterprise-4.13


Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
</details>
author_association: NONE
user: login: jab-rh
created_at: 2025-04-28T00:37:25Z
body: @anarnold97, looks like this needs a manual cherry pick to 4.13.
author_association: CONTRIBUTOR
user: login: anarnold97
created_at: 2025-04-28T08:52:23Z
body: @jab-rh - apologies. MTC 1.8 should only go into OCP 4.14 and later - https://access.redhat.com/support/policy/updates/openshift_operators

although i also i need to update the operators lifecycle page  
author_association: CONTRIBUTOR