-
Bug
-
Resolution: Unresolved
-
Major
-
CNV v4.20.0, CNV v4.19.6
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
Release Notes
-
I suggest that in the known issue, we describe that migrations could be stuck due to a bug in the OCP-Virt UI. To work around the issue, one can use either the MTC UI (as was done prior to 4.19) or create MigPlan resources using the CLI.
-
Known Issue
-
Proposed
-
-
None
Description of problem:
The status of the migration plans was "The migration plan was previously used for Storage Conversion. It can only be used for further Storage Conversions. Other migrations will be possible only after a successful rollback is performed." It was determine with engineering that the migrateState: true in the MigMigration and should have been false. Updated the MigMigration and waited for migration plan to kick. Still didn't correct the issue. Engineering had us use the MTC GUI and the plan completed successully. Issue is with the working plan accessMode: auto broken plan accessMode: Auto
Version-Release number of selected component (if applicable):
CNV 4.19.6
How reproducible:
Attempt a storage live migration. Engineer recreated the issue on his 4.20 cluster as well.
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- links to
- mentioned on
