mysql upstart job is extremely confusing and unnecessary with sysvinit script from Percona

[Clint Byrum]

Having an upstart job which doesn't actually track a process's real state is very confusing, as sometimes the process is started without informing the upstart job.

The stated goal of the original change is also not actually possible with upstart, since OpenStack and MySQL are part of a distributed system. We would have to SSH to the MySQL service and start it instead of just hoping that the local MySQL satisfies all of the needs of the local OpenStack components. Instead, OpenStack components should be tolerant of temporarily unavailable MySQL, since it may be on a completely remote system, and recover gracefully when it is available.

[Clint Byrum (clint-fewbar)]

An alternative approach is to change the name of the upstart job from 'mysql' to something like 'mysql-boot-control' so it doesn't interfere with the 'service' command and other tools that may want to control the mysql service directly.

[Therese McHale (therese-mchale)]

https://review.openstack.org/#/c/99964/ provides a mysql-boot-control upstart

[Steven Hardy (shardy)]

This bug was reported against an old version of TripleO, and may no longer be valid.

Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.

Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]