neutron bootstrap container fails due to missing neutron.conf

[Hui Kang]

I observe that somehow the neutron-bootstrap node fails due to missing /etc/kolla/neutron-server/neutron-conf on the host.

This problem should be fixed by creating the neutron bootstrap container on the neutron-server or network, rather than any nova nodes.

- Hui

[Hui Kang (huikang27)]

Another alternative solution is to push the neutron.conf to all the nodes, include the compute nodes.

[Hui Kang (huikang27)]

    - name: Starting Neutron bootstrap container
      docker:
        ........
      volumes: "{{ node_config_directory }}/neutron-server/:{{ container_config_directory }}/:ro

If this role is run on a compute node, the neutron-server directory will be empty

- Hui

[Ryan Hallisey (rthall14)]

Looks like this is fixed in https://review.openstack.org/#/c/241989/3

[Hui Kang (huikang27)]

Hi, Ryan
I found that Sam's patch does not solve this issue completely. Chances are that the bootstrap playbook runs on a node which does not create the database user. Then the bootstrap will not happen.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/242907
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=4ad8db71683915a771788815bf1894237975f982
Submitter: Jenkins
Branch: master

commit 4ad8db71683915a771788815bf1894237975f982
Author: Sam Yaple <email address hidden>
Date: Mon Nov 9 02:59:17 2015 +0000

    Remove unused cinder-data container

    The cinder-data container serves no purpose and is not actually used
    past the bootstrap container and should be removed.

    Additionally add the missing '---' header to the start.yml file.

    TrivialFix
    Related-Bug: #1513598
    Related-Bug: #1513439
    Change-Id: I22b630bbee954e12a4de5652b7fb068669f633c5

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/242908
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=564f8f2bd484181ea46041932befbbe9bc67afb3
Submitter: Jenkins
Branch: master

commit 564f8f2bd484181ea46041932befbbe9bc67afb3
Author: Sam Yaple <email address hidden>
Date: Mon Nov 9 03:06:31 2015 +0000

    Move data container to start.yml

    The original reason for having the data container in the bootstrap.yml
    was to keep consistency with rabbitmq and mariadb, but in light of
    this bug we need to move the data container out of the bootstrap.yml
    role since we will be limiting the hosts that those tasks can run on.

    Change-Id: I7f2f5979b01807275908699d1243756cb97d3588
    Partial-Bug: #1513598

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/248148
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=07023839104e99ab1e6e2562bf610ab52ddb8909
Submitter: Jenkins
Branch: stable/liberty

commit 07023839104e99ab1e6e2562bf610ab52ddb8909
Author: Sam Yaple <email address hidden>
Date: Mon Nov 9 03:06:31 2015 +0000

    Move data container to start.yml

    The original reason for having the data container in the bootstrap.yml
    was to keep consistency with rabbitmq and mariadb, but in light of
    this bug we need to move the data container out of the bootstrap.yml
    role since we will be limiting the hosts that those tasks can run on.

    Change-Id: I7f2f5979b01807275908699d1243756cb97d3588
    Partial-Bug: #1513598
    (cherry picked from commit 564f8f2bd484181ea46041932befbbe9bc67afb3)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/242777
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=790bf336d5e082c5c079bfb681f9509188eae72f
Submitter: Jenkins
Branch: master

commit 790bf336d5e082c5c079bfb681f9509188eae72f
Author: Hui Kang <email address hidden>
Date: Sat Nov 7 15:11:40 2015 -0500

    Fix bootstrap for services

    The bootstrap tasks could be started on any node listed in the
    site.yml

    The issue is that all the tasks must run on the same node, and the
    only node that all the tasks can run on is the 'api' node due to
    needing to start the bootstrap container which binds in the configs.

    delegate_to is required to ensure that the proper node gets the task.

    Co-Authored-By: Sam Yaple <email address hidden>
    Change-Id: Ica04ab366777a571a92212ac22c482f1881d4ecd
    Closes-Bug: #1513598
    Related-Bug: #1513439

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/248958
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=f099c6ed59e0c60ed3efa9e43694dec5c5c07ece
Submitter: Jenkins
Branch: stable/liberty

commit f099c6ed59e0c60ed3efa9e43694dec5c5c07ece
Author: Hui Kang <email address hidden>
Date: Sat Nov 7 15:11:40 2015 -0500

    Fix bootstrap for services

    The bootstrap tasks could be started on any node listed in the
    site.yml

    The issue is that all the tasks must run on the same node, and the
    only node that all the tasks can run on is the 'api' node due to
    needing to start the bootstrap container which binds in the configs.

    delegate_to is required to ensure that the proper node gets the task.

    Co-Authored-By: Sam Yaple <email address hidden>
    Change-Id: Ica04ab366777a571a92212ac22c482f1881d4ecd
    Closes-Bug: #1513598
    Related-Bug: #1513439
    (cherry picked from commit 790bf336d5e082c5c079bfb681f9509188eae72f)

[Sam Yaple (s8m)]

Hui you have reopened this without adding new information. If this is still an issue for you please add the information I requested in those patchsets to a new bug report. Adding new patchsets to this bug will mess with tracking.

As for the report in this bug report (as well as all the dups pointed to this), this bug is resolved for those issues.

Please open a new bug with all the info requested as well as steps to duplicate your issue.