| 2017-05-23 19:57:19 |
Andrew Bruce |
description |
Just deployed Kolla following guide at https://docs.openstack.org/developer/kolla-kubernetes/deployment-guide.html
Problem is that neutron-dhcp-agent, neutron-l3-agent, and neutron-metadata-agent all fail to start because the ml2-conf.ini key is missing from the generated configMap.
The cause is a mismatch between kolla-ansible and kolla-kubernetes. Both contain a file named 'ansible/roles/neutron/tasks/config.yml' and the two files are different. Specifically, see services_need_ml2_conf_ini.
Check out the fork at https://github.com/andybrucenet/kolla-ansible. I'll submit a pull request after I see that this bug has been reviewed. |
Just deployed Kolla following guide at https://docs.openstack.org/developer/kolla-kubernetes/deployment-guide.html
Problem is that neutron-dhcp-agent, neutron-l3-agent, and neutron-metadata-agent all fail to start because the ml2-conf.ini key is missing from the generated configMap.
The cause is a mismatch between kolla-ansible and kolla-kubernetes. Both contain a file named 'ansible/roles/neutron/tasks/config.yml' and the two files are different. Specifically, see services_need_ml2_conf_ini (file https://github.com/andybrucenet/kolla-ansible/blob/dec8fbd7a463ab58d5d5455fcfc45b0302c1a707/ansible/roles/neutron/tasks/config.yml)
Check out the fork at https://github.com/andybrucenet/kolla-ansible. I'll submit a pull request after I see that this bug has been reviewed. |
|
