[Bug 959426] Re: nova services start before mysql on boot

[Adam Gandelman]

The fix in bug 943031 was recently re-implemented in Glance @ https://review.openstack.org/#change,5552  While this change currently doesn't resolve the issue of an unreachable database on service startup, it can easily be extended to check the ability to actually connect thru the sqlalchemy engine at startup / during configure_db().   It's been mentioned that the same logic should be a part of nova or openstack-common as well.  If it lands there, it will also resolve this issue for nova.   

Marking as critical in Ubuntu,  adding a task for Glance + tagging
essex-rc-potential as this is a serious issue for anyone expecting these
services to start reliably.

Note, Keystone seems to initialize its database lazily and not touch
till a request comes in.  I'm not sure about quantum?

** Also affects: glance
   Importance: Undecided
       Status: New

** Changed in: nova (Ubuntu)
   Importance: Undecided => Critical

** Also affects: glance (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- nova services start before mysql on boot
+ nova + glance services die if started before db is reachable

-- 
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 + glance services die if started before db is reachable

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/959426/+subscriptions