Bug 1408834
| Summary: | [SR-IOV] - VF leakage on destination host in case of migration failure | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
| Component: | BLL.Network | Assignee: | Arik <ahadas> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.1.0 | CC: | ahadas, bugs, danken, ylavi | ||||
| Target Milestone: | ovirt-4.1.0-beta | Flags: | rule-engine:
ovirt-4.1+
|
||||
| Target Release: | 4.1.0.2 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.1.0-0.4.master.20170105161132.gitf4e2c11.el7.centos.noarch.rpm | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-02-01 14:54:59 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Verified on - 4.1.0-0.4.master.20170105161132.gitf4e2c11.el7.centos Now, in case of migration failure, the reserved vf on destination host doesn't leak and can be used. |
Created attachment 1235520 [details] Logs Description of problem: [SR-IOV] - VF leakage on destination host in case of migration failure. Assuming that engine allocated VFs on the destination host, and started migration on Vdsm. However, migration has failed (a bug in Vdsm or timeout or failure to contact the destination), in such migration failure there is a vf leakage on destination host and the reserved vf can't be allocated to other VMs, until shutting down the vm on source host. Version-Release number of selected component (if applicable): 4.1.0-0.3.beta2.el7 Steps to Reproduce: 1. Try to migrate vm with sr-iov vNIC(engine allocate vfs on destination) and brake the connection on the destination 2. Once destination host is up, try to use the reserved vf Actual results: Failed. vf leakage on the destination host, Engine still consider the vf as taken. On the destination host the vf is free. Once shutting down the vm on source host, the vf released. Expected results: In case of migration failure, the reserved vf shouldn't leak.