This is not resolved by the fix for bug 943031 which, AFAICS, fixes the issue of an existing db connection going away. The bug here is at service start up, ie starting nova-compute with a mysql server that is not up (yet) ends in:
(nova): TRACE: OperationalError: (OperationalError) (2003, "Can't connect to MySQL server on 'outo.home.base' (111)") None None and a dead process. Initial setup of the database connection does not retry, and instead the service dies (quickly). This can't really be worked around in packaging/upstart and shouldn't need to be, as a database is truly and external resource anyway. In contrast, the rabbitmq connection initialization loops at start up if it cannot connect to its server, dumping tracebacks to nova-$foo.log but at least keeps the service up and makes a connection when the server appears. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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/nova/+bug/959426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
