Bug 1990581
| Summary: | [DOC] Migration plan not progressing without indicating the cause in UI | ||
|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Ilanit Stein <istein> |
| Component: | Documentation | Assignee: | Avital Pinnick <apinnick> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Amos Mastbaum <amastbau> |
| Severity: | high | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | unspecified | ||
| Version: | 2.1.0 | CC: | amastbau, apinnick, fdupont, istein |
| Target Milestone: | --- | ||
| Target Release: | 2.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-19 10:40:37 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
The "Disk copy stage does not progress" section LGTM. Moving bug to VERIFIED. Changes will be merged when all issues in the PR are verified. |
Description of problem: In MTV-2.1 there are cases that the migration plan will show as if it's running, with no progress in the disk copy. This cannot be fixed within MTV-2.1 time frame. It is planned to get it fixed in MTV-2.2. Please document in MTV=2.1 Trouble shooting section the below information: There might be various reasons causing the migration plan to be in such a state: 1. No suitable target storage as required. 2. Missing vddk-init-image configuration on the OCP cluster. 3. VM has no disk. 4. One of the validation rules fails the VM import, but the error is not propagated to the migration plan. Examples: a. VM is set to be Migratable (affinity policy) - For this we will also need to document RHV procedure to how change VM to be non migratable (pinned to host), or redirect to the RHV Doc. b. VM has USB. The issue is usually displayed in the migration plan create page, by the validation service, as a critical warning, but if the user will miss/ignore it, the migration plan will be at the state described above. Also the cause is usually indicated besides the failing VM import object, in the Openshift workloads->Virtualization page. ** 1, 2 might already be documented in the MTV Document. Version-Release number of selected component (if applicable): MTV-2.1