Bug 1901848
| Summary: | Adding information regarding 'Copying Data' phase: Started/Completed/In Progress for each disk | ||
|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Maayan Hadasi <mguetta> |
| Component: | User Experience | Assignee: | Arik <ahadas> |
| Status: | CLOSED MIGRATED | QA Contact: | Maayan Hadasi <mguetta> |
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> |
| Priority: | medium | ||
| Version: | 2.0.0 | CC: | ahadas, fdupont, istein, jortel |
| Target Milestone: | --- | Keywords: | RFE |
| Target Release: | 2.4.0 | Flags: | mturley:
needinfo?
(jortel) mturley: needinfo? (fdupont) mturley: needinfo? (jortel) |
| 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: | 2023-07-12 16:57:46 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: | |||
Not ready for 2.0.0. Moving to 2.1.0. @jortel, am I correct in assuming that this would require additional status data in the API? This would also require new design work.. Fabien, are we ok with moving this to 2.2.0 to focus on hooks and RHV migration? Deal. Hooks and RHV are higher priority. Fabien, am I correct in assuming this will be part of the new Settings page that still needs backend work, so it should be in 2.4.0? Sorry, I intended the above comment for a different BZ. I do think we may need to push this back to 2.4.0 though since it still needs backend work and design. @jortel do you have any thoughts on trying to do this for 2.3.0? |
Description of problem: There could be cases that by looking in MTV UI it seems as the disk copy was started, but actually it wasn't. For example, in case of vddk-init image is missing in v2v-vmware ConfigMap and an API migration is executed -> vmimport CR is created but is not running actually, and in MTV UI the copyingDisk for this VM seems to be in progress Expected results: To track the copying disk progress for each VM migration and to catch the cases where the copy wasn't started or got stuck. Additional info: By Jeff Ortel: Within the DiskTransfer step in the pipeline there is a list of Tasks (one for each disk) which contains all of the same fields as a Step including: Started (timestamp) Completed (timestamp) Progress { total: n, completed: n} Phase as reported on in the DataVolume status.