My current workaround is:
1. remove all compute nodes from inventory file, only leave controller and network node (they are the same host in my environment)
2. run deployment with this inventory file
3. add back compute nodes in inventory file
4. modify
kolla/ansible/roles/neutron/tasks/bootstrap.yml
change
It is mandatory to use the original bootstrap.yml to finish the initial deployment on controller node (correct database will be created in this step), then do the modification and deploy to compute node again. If run deployment with modified bootstrap.yml directly on a fresh multi-node deployment, the deployment will succeed but neutron cannot start because the missing of service/endpoint in keystone and databases in mariadb.
My current workaround is: roles/neutron/ tasks/bootstrap .yml
1. remove all compute nodes from inventory file, only leave controller and network node (they are the same host in my environment)
2. run deployment with this inventory file
3. add back compute nodes in inventory file
4. modify
kolla/ansible/
change
set_fact: created: "{{ (database. stdout. split(' localhost | SUCCESS => ')[1]|$
database_
to
set_fact: created: "true"
database_
run deployment again.
It is mandatory to use the original bootstrap.yml to finish the initial deployment on controller node (correct database will be created in this step), then do the modification and deploy to compute node again. If run deployment with modified bootstrap.yml directly on a fresh multi-node deployment, the deployment will succeed but neutron cannot start because the missing of service/endpoint in keystone and databases in mariadb.