diff options
| author | Serguei Bezverkhi <sbezverk@cisco.com> | 2017-07-16 15:11:46 -0400 |
|---|---|---|
| committer | Serguei Bezverkhi <sbezverk@cisco.com> | 2017-07-16 15:15:47 -0400 |
| commit | 5e07cc1ab4e1d96632ac961f1c11b68bcff6fbdd (patch) | |
| tree | 91c83667e9e39cb1a7bbb5841471aaf1de08bc48 | |
| parent | e4245aa41596e921a8d5ef2a8c173884d446bc8a (diff) | |
| download | kolla-5e07cc1ab4e1d96632ac961f1c11b68bcff6fbdd.tar.gz kolla-5e07cc1ab4e1d96632ac961f1c11b68bcff6fbdd.zip | |
Fixing mariadb bootstrap failure in kolla-kubernetes
With latest master, mariadb is failing to bootstrap in kolla-kubernetes
cluster. The issue is with the name of mysql pid file. When it is not forced
in the command line, in kolla kubernetes it gets created in the form of
mariadb-init-element-xqg4b.pid where mariadb-init-element-xqg3b is pod name,
but bootstrap scripts explicitely checks for mysql.pid.
Change-Id: Ic0ee577d73d196ef40354efa51ca3ba60bf4e125
Closes-Bug: #1704671
| -rw-r--r-- | docker/mariadb/extend_start.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docker/mariadb/extend_start.sh b/docker/mariadb/extend_start.sh index 06bb8b4f4..1402a6381 100644 --- a/docker/mariadb/extend_start.sh +++ b/docker/mariadb/extend_start.sh @@ -1,7 +1,7 @@ #!/bin/bash function bootstrap_db { - mysqld_safe --wsrep-new-cluster --skip-networking --wsrep-on=OFF & + mysqld_safe --wsrep-new-cluster --skip-networking --wsrep-on=OFF --pid-file=/var/lib/mysql/mariadb.pid & # Wait for the mariadb server to be "Ready" before starting the security reset with a max timeout # NOTE(huikang): the location of mysql's socket file varies depending on the OS distributions. # Querying the cluster status has to be executed after the existence of mysql.sock and mariadb.pid. |