Bug 1434828

Summary: hosts config should be configured 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, sgaddam, slinaber, trozet
Target Milestone: rcKeywords: Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-neutron-10.3.0-2.el7ost openstack-tripleo-heat-templates-6.0.0-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
N/A
Last Closed: 2017-05-17 20:11:25 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:

Description Itzik Brown 2017-03-22 12:45:27 UTC
Description of problem:
Host config parameters should be configured in the OVSDB of every overcloud node.
Neutron uses host specific information while doing port-binding.
When using OpenDaylight is configuration is not set so Instances fail to start.


Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-6.0.0-0.20170307170102.3134785.0rc2.el7ost.noarch

How reproducible:


Steps to Reproduce:
1.Using opendaylight launch an instance and verify it fails to start.
2.In Neutron log verify you see the message 'ODL hostconfigs REST/GET failed, will retry on next poll'
3.

Actual results:


Expected results:


Additional info:

Comment 7 Itzik Brown 2017-04-18 11:35:53 UTC
Able to start Instances.

Checked that ml2_odl section in /etc/neutron/plugins/ml2/ml2_conf.ini has:
port_binding_controller=network-topology

Checked with:
puppet-neutron-10.3.0-2.el7ost.noarch
openstack-tripleo-heat-templates-6.0.0-5.el7ost.noarch

Comment 8 errata-xmlrpc 2017-05-17 20:11:25 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