Bug 1532674
Summary: | Engine should update neutron that binding host has been changed after VM migration with neutron network | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
Component: | BLL.Network | Assignee: | Marcin Mirecki <mmirecki> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 4.2.0 | CC: | bugs, lveyde, ylavi | ||||
Target Milestone: | ovirt-4.2.2 | Flags: | rule-engine:
ovirt-4.2+
ylavi: exception+ |
||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | ovirt-engine-4.2.2.1 | Doc Type: | Bug Fix | ||||
Doc Text: |
This change is only valid when a vm having vnic connected to an external network is migrated.
After a successful migration, the engine will the external network provider about the fact that the vnic should now be bound on another host.
The request to the external provider will update the binding:host_id value of the port.
|
Story Points: | --- | ||||
Clone Of: | |||||||
: | 1549030 1549033 (view as bug list) | Environment: | |||||
Last Closed: | 2018-03-29 11:14:12 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1549030, 1549033 | ||||||
Attachments: |
|
Description
Michael Burman
2018-01-09 14:50:53 UTC
Created attachment 1379137 [details]
Logs
Verified on - 4.2.2.1-0.1.el7 with: vdsm-4.20.19-1.el7ev.x86_64 Red Hat OpenStack Platform release 12.0 (Pike) opendaylight-6.2.0-4.el7ost.noarch This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |