container cinder_api_db_sync fails with TLS everywhere

[Damien Ciabrini]

When cinder services are containerized, deployment of overcloud fails due to the cinder_api_db_sync not being able to connect to the database and start its setup.

This specific container is not managed by Kolla, so the puppet generated configuration files for cinder are not copied into the container.

By looking at the t-h-t definition, this container misses a bind-mount to let cinder access /etc/my.cnf.d/tripleo.cnf. Consequently, the SSL configuration is not being used and the setup fails.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/539498
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=6381879a1be11e6e1c8c9fb9f6faf6f6412b4b5f
Submitter: Zuul
Branch: master

commit 6381879a1be11e6e1c8c9fb9f6faf6f6412b4b5f
Author: Damien Ciabrini <email address hidden>
Date: Wed Jan 31 11:01:53 2018 +0000

    Bind mount the database client settings in cinder_api_db_sync

    cinder_api_db_sync does not use the database settings which are
    generated by the puppet_config step. Consequently, it loses some
    important client settings for accessing the DB, e.g. it breaks
    when TLS everywhere is enabled.

    Bind mount the tripleo.cnf file to expose the proper DB settings.

    Change-Id: I17f3304d546eeb78803b4a3cc859255bfb3f71eb
    Closes-Bug: #1746491

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 8.0.0.0rc1 release candidate.