d5e5e885d1
A common class of problems goes like this: * kolla-ansible deploy * Hit a problem, often in ansible/roles/*/tasks/bootstrap.yml * Re-run kolla-ansible deploy * Service fails to start This happens because the DB is created during the first run, but for some reason we fail before performing the DB sync. This means that on the second run we don't include ansible/roles/*/tasks/bootstrap_service.yml because the DB already exists, and therefore still don't perform the DB sync. However this time, the command may complete without apparent error. We should be less careful about when we perform the DB sync, and do it whenever it is necessary. There is an argument for not doing the sync during a 'reconfigure' command, although we will not change that here. This change only always performs the DB sync during 'deploy' and 'reconfigure' commands. Change-Id: I82d30f3fcf325a3fdff3c59f19a1f88055b566cc Closes-Bug: #1823766 Closes-Bug: #1797814 |
||
|---|---|---|
| .. | ||
| action_plugins | ||
| group_vars | ||
| inventory | ||
| library | ||
| roles | ||
| bifrost.yml | ||
| certificates.yml | ||
| destroy.yml | ||
| detect-release.yml | ||
| gather-facts.yml | ||
| kolla-host.yml | ||
| mariadb_backup.yml | ||
| mariadb_recovery.yml | ||
| post-deploy.yml | ||
| site.yml | ||