Description of problem: When importing a vm with v2v feature (doesn't matter what the source is), the vm appears in the system right away with status 'down' and then when the image is starting to copy to SD, the status in the UI changes to 'Copying disk 1/(number of disks)'. In REST API the status is 'down' all through the process (as in DB the status is always down). We need to reflect the status from UI to REST API as well, so user has some indication of the copying process. Version-Release number of selected component (if applicable): 4.1.0-0.0.master.20161112231308.git672bd31.el7.centos How reproducible: always Steps to Reproduce: 1. Import a vm via v2v from KVM provider or VmWare. 2. Sample status of the vm once it appears in the system, via REST API and UI Actual results: vm status changes to 'Copying disk' in UI and stays at status 'down' in API. Expected results: UI and API values should be the same. Additional info:
This information should be loadable the same way as the migration progress. So, it needs to be added to the VmStatisticalQuery.
The status is change in the UI and not part of the VM status, The status is actually right since the VM status is down - the REST way is to add status_detail as you can see here: <status>down</status> <status_detail>Copying disk 1/1</status_detail>
Verify with: Version 4.2.0-0.0.master.20170725202023.git561151b.el7.centos Steps: 1. Start V2V import process 2. Check VM status_detail via REST API, status_detail should be Copying disk 3. Check VM status_detail after importing finished, status_detail should be None PASS
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.