Public bug reported:
I've got a system where all the controller-type services (glance, api,
scheduler, rabbit, etc) are all on the same machine as the mysql DB, and
the compute nodes are on the same network.
When I reboot my precise machine, the logs are full of "could not
connect to mysql" errors, and half the services aren't running. The
upstart scripts should probably make an allowance for starting
everything up after databases, or the services should re-try the
connections for a while before giving up and crashing.
** Affects: nova (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/959426
Title:
nova services start before mysql on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/959426/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
