Comment 2 for bug 1331478

This trace is expected and isn't a problem: on Ubuntu, cinder-scheduler is started when package is installed, before it was configured (11:21:55 in the logs). Right before that, cinder.conf is updated with MySQL connection details (11:21:51), so cinder-scheduler tries to use that but can't yet, because cinder user is created in MySQL a few minutes later (11:26). As soon as cinder configuration is done, cinder-scheduler is restarted (11:33), and at that time all Cinder services are able to connect successfully.