Description of problem: On version hco-bundle-registry:v2.0.0-33, there are several problems with current implementation of the v2v migration progress display in the UI: 1. In conversion pod log these periodic messages appear: "Updating progress on pod annotation". (The progress percent is not detailed in the log itself). Clicking the Pod Overview -> Click 'Annotation (2)' button show percent value,but once this window is open, the displayed percent is not progressed, though migration is progressing.In order to view any progress, need to close it, and open it again. So first problem id that the display on this value is not dynamic. 2. When the migration progress percent is populated with values (other than the initial 0 value) , the values are not rounded. For example it displays 13.14, and eventually it displays something like 99.31 (It do not reach 100 (%)). So second problem is that percent is not rounded. and third that it do not reach 100% Would be good to have instead, something like a progress bar display as we have is in RHV/CFME, or at least some value that is progressed dynamically, while migration is progressing.
Jira ticket: https://jira.coreos.com/browse/KNIP-806
This is the patch https://github.com/openshift/console/commit/501783c2b68c4d4dbbdecfc8247e0379f8e61088 adding the support to show the v2v import progress as a progress bar in the dashboard.
This should be fixed already.
Tomas, While VM import, a progress bar for the imported VM is indeed displayed, but it remains on progress 0%. The conversion Pod's Annotation progress also did not show progress beyond 0%, Might be that there is some basic problem with the progress reporting, and not necessarily with the progress bar. I can provide the environment details. Would you please take a look?
if the pod keeps showing 0%, UI will only display it. @Tomas: any changes in this area?
I am little bit confused here. So is the bug about the fact that the annotation does not show 100% when the conversion is done or about something else? Anything else sounds like UI issue to me.
> I am little bit confused here. So is the bug about the fact that the annotation does not show 100% when the conversion is done or about something else? Anything else sounds like UI issue to me. IIUC the problem is that the annotation only shows 0% during the whole migration.
What is the version of the container?
I tested another VM migration, of a RHEL8 with 25GB disk. During the disk conversion I tracked the pod's v2v log. Unlike in past versions, I could not see progress percent messages, from time to time in the log. These messages appear in the log: "DEBUG - Updating progress in POD annotation" however, Pod Annotations, Key "v2vConversionProgress", show value 0% all along the VM migration. Tomas G. checked my environment (CNV-2.3 latest version) and found that this no progress issue is due to Bug 1810040 - "Migration progress status in virt-v2v-wrapper.log gets skipped", solved in v2v-wrapper package 2.2.0 or newer, but CNV-2.3 latest version, contains v2v-wrapper package version 1.15.0. Filed this Bug 1829828 - [v2v][Doc] VM migration progress percent is not progressing Based on the above this bug can't be verified on CNV-2.3.
based on comment 14 moving this bug to the next release
This is the BZ to track the no progress on the beck end, for CNV: Bug 1830780 - virt-v2v-wrapper - 0% VM migration progress in UI
Verification is blocked by Bug 1845183 - [v2v] VMware to CNV: VM import fails quickly on "Failed to get watch namespace". VM import do not reach the stage of disk copy right now.
Verified on CNV-2.4. Progress bar is progressing a couple of munutes after VM import is trigered. Tested with RHEL-7 VM import. The progress bar is seen progressing both on "Overview" page, and when clicking the imported VM status, while import is not yet done.
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, 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/RHSA-2020:3194