Bug 1990596
| Summary: | Improve VM status messages on "Migration plan details" page when migration plan hangs | ||
|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Ilanit Stein <istein> |
| Component: | Controller | Assignee: | Sam Lucidi <slucidi> |
| Status: | CLOSED ERRATA | QA Contact: | Ilanit Stein <istein> |
| Severity: | high | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | high | ||
| Version: | 2.1.0 | CC: | fdupont |
| Target Milestone: | --- | ||
| Target Release: | 2.2.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-12-09 19:20:47 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: | |||
|
Description
Ilanit Stein
2021-08-05 17:03:49 UTC
This bug is fairly vague, but I think the majority of cases have probably been fixed due to 2.2.0's improved status reporting. Please verify with mtv-operator-bundle-2.0.0-57 / iib:126435, or later. The cases in Bug 1990581 were checked on MTV-2.2.0-84 - Details below. 1. No suitable target storage as required. Case: Migration from VMware of a 100GB disk, to NFS, when there is no PV in such a size on the cluster Result: Migration UI show migration plan is in "Transfer disk" phase, with status "Pending" - No clear reason to what it is pending. 2. Missing vddk-init-image configuration on the OCP cluster. Case: No vddk-init-image configured. Result: Migration UI show migration plan is stuck in "Initialize" phase, with no indication on that it is waiting for vddk. Bug 2015813 - Reflect "no VDDK init image" state in Migration UI by changing MTV API should address this. 3. VM has no disk. A a migration plan for a VM with no disk cannot be created in the UI, since the storage mapping step cannot be skipped. Therefore, this case is not valid when running migration from UI. 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. A VM is migrated from RHV regardless to the affinity policy. In case it is set as "Migratable" there is a validation warning. The migration pass and do not hang. 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. A RHV VM that has a USB Mapped host device or Console: USB enabled pass migration and do not hang. there is a validation warning on that. ================== Cases 1 & 2 still hang the plan with no clear displayed reason. They need to be fixed. Cases 3 & 4[a,b] are no longer hanging the plan. Moving this bug to verified since some of the cases are solved, and for the ones that are not there are separate bugs. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (MTV 2.2.0 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:5066 |