Comment 3 for bug 1537945

Findings so far:
================
Two issues reported in this bug are, wrong status reported by openstack-status and mysql not coming up after reboot.

openstack-status reports mysql as inactive (disabled on boot), even though mysql is running.

== Support services ==
mysql: inactive (disabled on boot)
libvirt-bin: active
rabbitmq-server: active
memcached: inactive (disabled on boot)
== Keystone users ==
Warning keystonerc not sourced
root@blaster-dgautam05:~# ps ax | grep mysql
19125 ? SN 0:00 /bin/sh /usr/bin/mysqld_safe
20525 ? SNl 2:59 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/log/mysql/error.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --wsrep_start_position=a8dae4c3-a30a-11e6-8f7f-773b1e577d7d:216982
22721 pts/2 S+ 0:00 grep --color=auto mysql
root@blaster-dgautam05:~#

for mysql not coming up after reboot, This is not a SM related issue as same issue has been reported in fab as well. see https://bugs.launchpad.net/juniperopenstack/+bug/1611566