Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

@shor52rus After fresh reboot of controller you should check your nova-scheduler.log, if there are these kind of errors:

OperationalError: (OperationalError) (2003, "Can't connect to MySQL server on 'controller' (111)") None None then it may be this problem https://ask.openstack.org/en/question/53602/services-start-up-priority-at-boot-on-controller/

@shor52rus After fresh reboot of controller you should check your nova-scheduler.log, if there are these kind of errors:

OperationalError: (OperationalError) (2003, "Can't connect to MySQL server on 'controller' (111)") None None None

then it may be this problem https://ask.openstack.org/en/question/53602/services-start-up-priority-at-boot-on-controller/

@shor52rus After fresh reboot of controller you should check your nova-scheduler.log, if there are these kind of errors:

OperationalError: (OperationalError) (2003, "Can't connect to MySQL server on 'controller' (111)") None None

then it may be this problem https://ask.openstack.org/en/question/53602/services-start-up-priority-at-boot-on-controller/problem