Hide Forgot
Description of problem: Custom role for OpenDaylight without Neutron API service fails due to coupled dependencies between ODL and the Neutron service which cause an isolated ODL role to fail deployment. The first is ODL service is invoking neutron services which really should be left up to the user to map based on custom roles. This needs to be removed. The second issue is Neutron ML2 config with OpenDaylight relies on knowing the heat parameters to be able to add the ML2 config. When OpenDaylight API service is isolated to its own role, the Controller Neutron ML2 service will not have the correct hiera variables to be able to configure ML2. The solution to this is to add those parameters to the OpenDaylight OVS service, which will also be used on the Controller. Version-Release number of selected component (if applicable): How reproducible: Always if OpenDaylightApi service is configured only on a custom role without Neutron services. Steps to Reproduce: 1. Assign OpenDaylightApi to its own role. 2. Deploy 3. Actual results: ML2 puppet config fails and OpenDaylightApi service fails while trying to configure neutron on the OpenDaylight role. Expected results: ML2 config should complete on Controller node (where Neutron is) and OpenDaylight node should not try to configure Neutron. Additional info:
Change 413205 proposed to master, and will need to be cherry picked to Newton.
All changes are merged upstream in stable/newton
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-0234.html