Bug 1341958
Summary: | Backport to liberty: Native ovsdb implementation not working | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Hynek Mlnarik <hmlnarik> |
Component: | openstack-neutron | Assignee: | Hynek Mlnarik <hmlnarik> |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 (Liberty) | CC: | adahms, amuller, chrisw, dcadzow, hmlnarik, ihrachys, nyechiel, srevivo |
Target Milestone: | async | Keywords: | FeatureBackport, ZStream |
Target Release: | 8.0 (Liberty) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-7.0.4-7.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, connectivity would never be enabled when attempting to use the new native OVSDB provider due to the db_set operation appearing to fail to change the patch ports from "nonexistant-peer" to the correct peer, thereby not linking the bridges together. This was caused by an incorrect method being used to set the peer interface of an OVS bridge. With this update, the peer option is now correctly set for both native and vsctl interfaces.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-29 13:59:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1340717 |
Description
Hynek Mlnarik
2016-06-02 07:13:10 UTC
Why do we care about the issue in OSP context? Do we use native interface anywhere? Yes, in functional tests. Namely functional tests for bug 1340717 fail if this patch is not included. Code tested in latest OSP8 - openstack-neutron-7.0.4-7.el7ost Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1353 |