Stale PID file after reboot preventing the service from starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Router Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
After an abrupt reboot of an Openstack control node due to a hardware problem, all mysql-router units running on that node enter blocked state. mysql-router service couldn't start on them due to stale PID files, for example:
Mar 04 03:09:31 juju-733f2f-
Mar 04 03:09:31 juju-733f2f-
Openstack API services were affected and couldn't re-connect to MySQL because of that, rendering 1/3 of the control-plane unhealthy.
The workaround was to manually remove stale PID files, restart *-mysql-router services and (optionally) restart affected Openstack services.
Versions:
focal-ussuri
MySQL router charm revision 6 from the stable channel
ii libmysqlclient-dev 8.0.28-
ii libmysqlclient2
ii mysql-common 5.8+1.0.5ubuntu2 all MySQL database common files, e.g. /etc/mysql/my.cnf
ii mysql-router 8.0.28-
ii python3-pymysql 0.9.3-2ubuntu3 all Pure-Python MySQL Driver - Python 3.x
Juju 2.9.46
Triaged as medium as there is a workaround (although it's manual).