startup race between MariaDB and nova services
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Community Project |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I've followed the instructions from http://
nova service-list
+----+-
| Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+----+-
| 1 | nova-cert | controller | internal | enabled | down | 2015-03-
| 2 | nova-consoleauth | controller | internal | enabled | up | 2015-03-
| 3 | nova-scheduler | controller | internal | enabled | down | 2015-03-
| 4 | nova-conductor | controller | internal | enabled | up | 2015-03-
| 5 | nova-compute | compute1 | nova | enabled | up | 2015-03-
+----+-
It is the same problem as described in https:/
I think the problem is, that MariaDB is started via /etc/init/S19mysql while the nova services are started via upstart. When the nova services are starting, mysql was not ready:
/var/log/
2015-03-16 09:21:36.253 930 TRACE nova.openstack.
/var/log/
2015-03-16 09:21:36.251 935 TRACE nova.openstack.
/var/log/
150316 9:21:39 [Note] /usr/sbin/mysqld: ready for connections.
If you look at the time stamps, mysql reported "ready" after the nova services had logged an error. Maybe that's the problem.
Try to use the support channels listed on https:/ /www.openstack. org/community# help