Handling of NeutronWorkers in neutron-metadata is wrong

[Brent Eagles]

I missed this for the neutron-metadata when updating neutron-api to use a conditions to handle default workers settings of empty strings. It is currently setting an empty string in the hieradata resulting in a bogus configuration for the workers on the server. This will need to be backported to ocata as it is a regression.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/463693
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=02a086bdb95fb55e920e0ff9307bc362e4d55979
Submitter: Jenkins
Branch: master

commit 02a086bdb95fb55e920e0ff9307bc362e4d55979
Author: Or Idgar <email address hidden>
Date: Wed May 10 09:50:51 2017 +0000

    Change neutron-metadata number of workers determination method

    neutron-metadata number of workers will be taken from NeutronWorkers parameter
    if not empty. when empty, all keys related to NeutronWorkers value will be
    set with empty dictionary instead empty string ({}).

    Change-Id: I18347639c188bbf085e2f3c739465e52c94b9d77
    Closes-bug: #1689571

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b2 development milestone.