Description of problem: On CFME v2v request, the progress stages, that can be monitored on RHV logs, are not reflected. Here are the steps the request do report on (by mbetak): (02:34:24 PM) mbetak: 1) submit vm import (but you probably won't catch that) (02:34:24 PM) mbetak: 2) waiting for import (02:34:24 PM) mbetak: 3) configuring vm networks When I tracked the Automate request what I sew was last message was irst lunch, and then it moved to wait for import. There seem to be also another problem in the request status. In cases the v2v operation fail immediately, like in case described in bug 1467795. The request status do not move to Failed, but rather does continues retries, with state: wait for import. Also, for cases import succeed, the CFME v2v request fail after timeout of ~2 days (bug 1469492). Version-Release number of selected component (if applicable): CFME-5.8.1/RHV-4.1.3 How reproducible: always. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1296217 [details] automation.log
Created attachment 1296225 [details] evm.log
Created attachment 1296235 [details] production.log
Created attachment 1296240 [details] rhevm.log
It looks like the issue is the same as in BZ #1469498 and BZ #1467795.
In reply to comment #6, This bug is about providing details within the request messages, about the import progress stages. Those stages can be seen in import log, on the RHV host.
(In reply to Ilanit Stein from comment #7) > In reply to comment #6, > > This bug is about providing details within the request messages, > about the import progress stages. > Those stages can be seen in import log, on the RHV host. not sure now what this bug is about. In description you mention 2 issues: 1: if the import passes, it does not move the state to success. It is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1469492 2: if the import fails, it does not move to error state. It is tracked by https://bugzilla.redhat.com/show_bug.cgi?id=1473169 Is this all so I can close this particular BZ or is this about something else?
In reply to comment #8: At the current implementation, the CFME v2v request show only "Wait for Import". This bug is for reporting import stages in the request, instead. For example, show: disk initializing, import percentage, etc.
there's no support ATM for reporting the stages over REST API. There might be a way of watching for disks and probing their progress perhaps. Not a 5.8.z material in any case
closing, since it's part of the old v2v solution.