db sync can time out for overcloud deploy

[Mike Bayer]

During overcloud deployment, particularly against Galera, the deployment can time out due to the db sync operation for both Nova and Neutron taking more than the puppet default of 300 seconds. The timeout here should be configurable to allow for longer upgrade periods, at least for when building up a database from scratch. As Openstack projects add more database migration steps, these timeouts will slowly become more prevalent.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/416298
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=a87b5630ba5d1d9f5a86c23701f5d5922120f72d
Submitter: Jenkins
Branch: master

commit a87b5630ba5d1d9f5a86c23701f5d5922120f72d
Author: Mike Bayer <email address hidden>
Date: Tue Jan 3 11:55:56 2017 -0500

    add configurable timeouts for DB sync

    This patch integrates with the db_sync_timeout
    parameter recently added to puppet-nova
    and puppet-neutron in
    I6b30a4d9e3ca25d9a473e4eb614a8769fa4567e7, which allow for the full
    db_sync install to have more time than just Pupppet's
    default of 300 seconds. Ultimately, similar timeouts
    can be added for all other projects that feature
    db sync phases, however Nova and Neutron are currently
    the ones that are known to time out in some
    environments.

    Closes-bug: #1661100
    Change-Id: Ic47439a0a774e3d74e844d43b58956da8d1887da

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b1 development milestone.