Critical error in cinder-scheduler log for Ubuntu, HA: (OperationalError) (2003, "Can't connect to MySQL server on '192.168.0.1' (111)") None None

Bug #1283037 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Fuel Library (Deprecated)

Bug Description

"build_id": "2014-02-21_13-53-24",
"mirantis": "yes",
"build_number": "176",
"nailgun_sha": "d528441c490fc53f26a9115fb866d41208727d1a",
"ostf_sha": "e74dcb33134d4334786a4fa27107febf9a497f2b",
"fuelmain_sha": "fe157dcc0c68a237b527cb9b6adf9101c815e374",
"astute_sha": "3d43abeefb60677ce6cae83d31ebbba1ff3cdbe2",
"release": "4.1",
"fuellib_sha": "a964b37f7f96f62a2f92b117c06077b53386a3ae"

1. Create new environment (Ubuntu, HA mode)
2. Choose VLAN segmentation
3. Add 3 controllers, 1 compute and 1 cinder
4. Choose Debug in 'OpenStack Settings' tab
5. Start deployment. It was successful
6. Critical error in cinder-scheduler log:

cinder [-] (OperationalError) (2003, "Can't connect to MySQL server on '192.168.0.1' (111)") None None

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Revision history for this message
Dmitry Ilyin (idv1985) wrote :

Does the mysql server work?

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

cinder-scheduler tried to start before haproxy backend for mysqld was enabled:

2014-02-21T11:26:20.904641+00:00 debug: 2014-02-21 11:26:18.964 6802 CRITICAL cinder [-] (OperationalError) (2003, "Can't connect to MySQL server on '192.168.0.1' (111)") None None
2014-02-21T11:29:32.757063+00:00 notice: (/Stage[main]/Openstack::Ha::Mysqld/Exec[wait-for-haproxy-mysql-backend]/returns) executed successfully

Changed in fuel:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Actually cinder-schedule was just running because it was started by the deb package. It was restarted by puppet after haproxy mysql backend was enabled:

2014-02-21T11:29:48.272560+00:00 debug: (Service[cinder-scheduler](provider=upstart)) Executing '/sbin/stop cinder-scheduler'
2014-02-21T11:29:48.510220+00:00 debug: (Service[cinder-scheduler](provider=upstart)) Executing '/sbin/start cinder-scheduler'

After that, it started successfully and reported no MySQL connection errors:

2014-02-21T11:29:52.169300+00:00 debug: 2014-02-21 11:29:51.040 1702 AUDIT cinder.service [-] Starting cinder-scheduler node (version 2013.2.2)

Changed in fuel:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.