4964ea2a76
Recently, the Postgresql backups were modified to generate drop database commands (--clean pgdumpall option). Also for single database restore, a DROP DATABASE command was added before the restore so that the database could be restored without duplicate rows. However, if there are existing database connections (by the applications or other users), then the drop database commands will fail. So for the duration of the restore database operation, the databases being restored need to have their existing connections dropped and new connections prevented until the database(s) restored, then connections should be re-allowed. Also found a problem with psql returning 0 (success code) even though there were errors during its execution. The solution is to check the output for errors and if there are any, dump out the log file for the user to see and let the user know there are errors. Lastly, a problem was found with the single database restortion, where the database dump for a single database was being incorrectly extracted from the psql dump file, resulting in the database not being restored correctly (most of the db being wiped out). This patchset fixes that issue as well. Change-Id: I4db3f6ac7e9fe7cce6a432dfba056e17ad1e3f06
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-alt on freenode
- Meeting Agenda Items: Agenda
- Join us on Slack
- #openstack-helm
Contributing
We welcome contributions. Check out this document if you would like to get involved.