summaryrefslogtreecommitdiffstats
path: root/recipes-extended/glusterfs/files/python-work-around-host-and-target-python.patch
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2018-03-29 15:29:13 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2018-04-03 23:23:43 -0400
commit8aa49d991123a954b404686cead6b58dc6de9242 (patch)
tree704261b38e135fc94228d8682c95676c46cdf3b1 /recipes-extended/glusterfs/files/python-work-around-host-and-target-python.patch
parent7db67a8eced8399d198bfa2cd6b9995f8842ead2 (diff)
downloadmeta-cloud-services-8aa49d991123a954b404686cead6b58dc6de9242.tar.gz
postgresql: don't attempt to start the DB before we setup the DB
When we boot the first time the postgresql service will [FAIL] and the following error is reported: pg_ctl[288]: pg_ctl: directory "/etc/postgresql/data" does not exist This is a result of the service being started before a call to postgresql's initdb is made on the PGDATA directory, usually made by the package's default 'postgresql-setup' or our 'postgresql-init' scripts. We split our 'postgresql-init' script into two, the first part which does the 'initdb' can be executed as part of the postgresql.service 'ExecStartPre' allowing the postgresql.service to not fail. The remainder of 'postgresql-init' script is executed as before, via the postgresql-init.service on first boot. This change also fixes some of the first boot startup races that was preventing some of the openstack '*-init' services which do DB configuration for openstack components from executing correctly. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-extended/glusterfs/files/python-work-around-host-and-target-python.patch')
0 files changed, 0 insertions, 0 deletions