Bug 1435320

Summary: provider_mappings is wrong when using OpenDaylight
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: openstack-tripleo-heat-templatesAssignee: Tim Rozet <trozet>
Status: CLOSED ERRATA QA Contact: Itzik Brown <itbrown>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 11.0 (Ocata)CC: jschluet, mburns, nyechiel, rhel-osp-director-maint
Target Milestone: rc   
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-6.0.0-0.9.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-05-17 20:13:18 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:

Description Itzik Brown 2017-03-23 14:25:25 UTC
Description of problem:

/etc/puppet/hieradata/service_configs.json has the following:
"neutron::plugins::ovs::opendaylight::provider_mappings": "[\"datacentre:eth2\"]",

It ends up with the following mapping:
{local_ip="172.17.2.16", provider_mappings="[datacentre:eth2]"}

Which is wrong (There shouldn't be square brackets)

Version
=======
openstack-tripleo-heat-templates-6.0.0-0.20170307170102.3134785.0rc2.el7ost.noarch

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install OpenStack with opendaylight_v2 mechanism driver
2. On one of the overcloud nodes run: ovstbl=$(ovs-vsctl get Open_vSwitch . _uuid); sudo ovs-vsctl get Open_vSwitch $ovstbl other_config
3. Verify the output is similar to the output in the description

Actual results:


Expected results:


Additional info:

Comment 1 Itzik Brown 2017-03-26 05:56:55 UTC
Fix was merged u/s in stable/ocata

Comment 4 Itzik Brown 2017-04-03 07:12:18 UTC
Verified with:
openstack-tripleo-heat-templates-6.0.0-0.9.el7ost.noarch

Comment 6 errata-xmlrpc 2017-05-17 20:13:18 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://access.redhat.com/errata/RHEA-2017:1245