Skip to content

Commit f2a8482

Browse files
anarnold97lpettyjo
andauthored
Update modules/migration-mtc-release-notes-1-8-6.adoc
Co-authored-by: Lisa Pettyjohn <[email protected]>
1 parent cc5f485 commit f2a8482

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/migration-mtc-release-notes-1-8-6.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ When migrating a Django and PostgreSQL application, the migration becomes fails
3838
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)]
3939

4040
.Persistent Volumes page hangs indefinitely for namespaces without persistent volume claims
41-
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)]
41+
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)]
4242

4343
[id="known-issues-1-8-6_{context}"]
4444
== Known issues

0 commit comments

Comments
 (0)