Description of problem:
When deploying OSPD with the following parameters the deployment fails.
Error: Could not find data item opendaylight_api_node_ips in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/neutron/plugins/ovs/opendaylight.pp:45 on node compute-0.localdomain
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The deployment execution:
openstack overcloud deploy --debug \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
--neutron-network-type vxlan \
--neutron-tunnel-types vxlan \
--control-scale 1 \
--control-flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 \--compute-scale 1 \
--compute-flavor compute-b634c10a-570f-59ba-bdbf-0c313d745a10 \--environment-file "/usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml" \
-e /home/stack/virt/network/network-environment.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/virt/hostnames.yml \
-e /home/stack/virt/debug.yaml \
-e /home/stack/neutron-opendaylight-l3.yaml \
--log-file overcloud_deployment_35.log &> overcloud_install.log
The neutron-opendaylight-l3.yaml file:
Output from heat 'deployment-show'
"deploy_stderr": "exception: connect failed\n\u001b[1;31mError: Could not find data item opendaylight_api_node_ips in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/neutron/plugins/ovs/opendaylight.pp:45 on node compute-0.localdomain\u001b[0m\n\u001b[1;31mError: Could not find data item opendaylight_api_node_ips in any Hiera data file and no default supplied at /etc/puppet/modules/tripleo/manifests/profile/base/neutron/plugins/ovs/opendaylight.pp:45 on node compute-0.localdomain\u001b[0m\n",
"status_reason": "deploy_status_code : Deployment exited with non-zero status code: 1",
After looking at this it looks like <service>_node_ips is now dynamically generated in THT (rather than the previous way declared in overcloud.yaml). The dynamic substitution is a little hard to follow, but my suspicion is the dynamic parsing is using the actual name of the service when it goes to parse <service name>Network. In this case the opendaylight service is 'OpenDaylight', but the ODL network is actually 'OpenDaylightApiNetwork'.
Itzik, can you please try chaning 'OpenDaylight' to be 'OpenDaylightApi' making these changes and redeploying?
It needs to be changed in these places:
Can you also verify that your original test included this patch?
My previous comment may not actually help (except to make things more aligned cosmetically).
Yes. It includes this patch.
After talking to Steve Hardy - there is a nuance to how TripleO interprets/translates the service net name into the <service_name>_network that includes splitting camel case with _ and setting to lower case. The issue was OpenDaylight is a single word with camel case, causing the translation to be:
open_daylight_api_node_ips, rather than opendaylight_api_node_ips. Steve has uploaded a fix:
I confirmed this works.
Can you please update the RPM version in 'Fixed in Version' ?
I'm not sure how to map upstream merged changes into downstream builds. But it has been some time since this was fixed upstream, it must be in the latest downstream build by now.
How do you suggest verifying? Make sure that the deployment is done?
Verified the the code openstack-tripleo-heat-templates-5.0.0-1.2.el7ost.noarch
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.