| Summary: | Vm status via REST API does not reflect 'Copying disk' when a vm is imported with v2v | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | sefi litmanovich <slitmano> |
| Component: | BLL.Virt | Assignee: | Shahar Havivi <shavivi> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Israel Pinto <ipinto> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | bugs, tjelinek |
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
ipinto: testing_plan_complete+ rule-engine: planning_ack+ rule-engine: devel_ack+ mavital: testing_ack+ |
| Target Release: | 4.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: | 2017-12-20 11:40:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
sefi litmanovich
2016-11-15 09:55:30 UTC
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. |