OVS OpenDaylight fails to configure correctly when TLS is used and connection uri's are set

[Tim Rozet]

There is a case in plugins::ovs::opendaylight where if TLS is enabled and the ovsdb URIs are passed in correctly as ssl, the values will not be propagated into the configuration for OVS due to missing else statements.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/536895

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/536895
Committed: https://git.openstack.org/cgit/openstack/puppet-neutron/commit/?id=707fad6f8959ba51897c599da30b3145bb66e2ef
Submitter: Zuul
Branch: master

commit 707fad6f8959ba51897c599da30b3145bb66e2ef
Author: Tim Rozet <email address hidden>
Date: Tue Jan 23 11:40:46 2018 -0500

    Fixes specifying OVSDB URIs with TLS for ODL OVS

    This fixes an issue with enabling TLS and specifying the OVSDB URI
    connection parameters for the ovs::opendaylight class. The settings
    were not being propogated into the OVS manager configuration when
    specified in the class.

    Closes-Bug: 1744967

    Change-Id: I004cffed10401a0132368375f0377a7aa45b5401
    Signed-off-by: Tim Rozet <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-neutron 12.3.0 release.