Bug 1394865 - ovsdb: don't erase existing ovsdb managers
Summary: ovsdb: don't erase existing ovsdb managers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z1
: 10.0 (Newton)
Assignee: Sridhar Gaddam
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks: 1258832
TreeView+ depends on / blocked
 
Reported: 2016-11-14 15:40 UTC by Itzik Brown
Modified: 2018-10-18 07:19 UTC (History)
8 users (show)

Fixed In Version: openstack-neutron-9.1.1-2.el7ost
Doc Type: Bug Fix
Doc Text:
The OpenStack Networking service supports two modes for ovsdb_interface, namely: 'vsctl' and 'native'. In Red Hat OpenStack Platform 9, the default mode was 'vsctl'. In the last version, the default changed to 'native'. In 'native' mode, when using Red Hat OpenStack Platform 10 with external controllers (such as ODL), the dhcp-agent overrode the OVS manager on the switch to loopback IP (ie. the default value of ovsdb_connection). As a result, the connection between the existing controller and the switch was lost. With this release, OpenStack Networking no longer overrides the manager on the switch. Rather, a new manager is added as necessary. This way, the connection between the switch and external controller stays intact.
Clone Of:
Environment:
N/A
Last Closed: 2017-01-26 16:41:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1614766 0 None None None 2016-11-14 15:40:06 UTC
OpenStack gerrit 403672 0 None None None 2016-12-01 13:40:52 UTC
Red Hat Product Errata RHBA-2017:0201 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-01-26 21:40:54 UTC

Internal Links: 1410937

Description Itzik Brown 2016-11-14 15:40:07 UTC 
Description of problem:
The current existing agent erases already set ovsdb managers entries. In some use cases, cloud admin sets ovsdb managers. eg, for SDN controllers or monitoring purpose. neutron agent shouldn't unconditionally erase the existing ovsdb managers.

Version-Release number of selected component (if applicable):
python-neutron-9.0.0-1.5.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Nir Yechiel 2016-11-30 13:45:13 UTC 
Cherry picked to branch stable/newton
Comment 2 Itzik Brown 2016-12-01 13:22:52 UTC 
For Director there is a fix in puppet-neutron
https://bugzilla.redhat.com/show_bug.cgi?id=1394861

The fix in neutron should be backported to Newton.
Comment 4 Sridhar Gaddam 2016-12-01 13:40:52 UTC 
Following is the fix in stable/newton (under review) https://review.openstack.org/#/c/403672/
Comment 12 Itzik Brown 2017-01-18 13:58:21 UTC 
Verified:
openstack-neutron-9.1.1-2.el7ost.noarch
Comment 14 errata-xmlrpc 2017-01-26 16:41:40 UTC 
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://rhn.redhat.com/errata/RHBA-2017-0201.html
Note You need to log in before you can comment on or make changes to this bug.