Bug 1655906
Summary: | After migration OSP13/14 OVN (or ODL) port status is DOWN | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Dominik Holler <dholler> | ||||||
Component: | BLL.Network | Assignee: | Dan Kenigsberg <danken> | ||||||
Status: | CLOSED DEFERRED | QA Contact: | Michael Burman <mburman> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 4.2.7.1 | CC: | amuller, bugs, mkalinin | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2018-12-18 11:34:34 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: |
|
Could this be related to RHV usage of non-standard tap device names, which should be fixed in https://gerrit.ovirt.org/#/c/96138/ ? (In reply to Dan Kenigsberg from comment #2) > Could this be related to RHV usage of non-standard tap device names, which > should be fixed in https://gerrit.ovirt.org/#/c/96138/ ? nope, it's not gone with nova-style tap names. If we get some help from openstack, we like to reopen this bug. Created attachment 1526767 [details]
OSP14 neutron log
|
Created attachment 1511233 [details] terminal log of migration Description of problem: If a VM with a vNIC on an external network provided by OSP13 Neutron with OVN ML2 plugin is migrated to another host, the port status is DOWN, but working. Version-Release number of selected component (if applicable): ovirt-4.2.8 How reproducible: Steps to Reproduce: 1. oVirt external network provider OSP13 Neutron with OVN ML2 plugin 2. Attach network of this provider to a vNIC 3. Migrate VM with this vNIC to another host Actual results: port status is DOWN after migration Expected results: port status is ACTIVE after migration