-
Bug
-
Resolution: Unresolved
-
Major
-
MTC 1.8.6
-
None
-
False
-
-
False
-
ToDo
-
-
Description:
A discrepancy exists in the reporting of namespace migration status following a rollback and subsequent re-migration attempt where the migration plan is deliberately faulted. Â Specifically, while the Distributed Volume Migration (DVM) phase correctly registers a failure, this failure is not consistently reflected in the user interface or the migration plan's YAML representation.
The failure of the DVM phase is only accurately displayed within the detailed migration view in the user interface.
The status.conditions field in the corresponding migration plan YAML does not include a condition that accurately reflects the DVM failure:
status:
conditions:
- category: Required
lastTransitionTime: "2025-04-14T14:47:43Z"
message: Persistent volumes have been discovered.
reason: Done
status: "True"
type: PvsDiscovered
- category: Required
lastTransitionTime: "2025-04-14T14:47:43Z"
message: Storage resources have been provisioned.
reason: Done
status: "True"
type: StorageEnsured
- category: Required
lastTransitionTime: "2025-04-14T14:47:43Z"
message: The migration plan is ready.
status: "True"
type: Ready
- category: Advisory
durable: true
lastTransitionTime: "2025-04-14T14:53:28Z"
message: This migration plan was previously used.
reason: NamespaceMigrationPlan
status: "True"
type: MigrationTypeIdentified
- category: Advisory
lastTransitionTime: "2025-04-14T14:53:29Z"
message: The migration plan is suspended.
status: "True"
type: Suspended
Â
Steps to reproduce:
- Create a namespace, deploy an application in it then migrate it
- Rollback
- set wrong cluster subdomain, then migrate
- observe the migration stauts
Â