Lost connection to MySQL server at 'reading initial communication packet'

[Stanislaw Bogatkin]

Fuel 10, current master, community ISO #659, problem caught on CI:
https://ci.fuel-infra.org/job/master.fuel-library.pkgs.ubuntu.smoke_neutron/7707/consoleFull

according to logs, OSTF failed when communicating with Nova and in Nova logs we see:

2016-09-13T01:29:54.499012+00:00 err: 2016-09-13 01:29:54.498 9013 ERROR nova.virt.driver [req-be70da4a-5466-4abd-8e04-4d4e3f2e33c2 - - - - -] Exception dispatching event <LifecycleEvent: 1473730176.46, 3a4c1c65-5d5e-4e8c-8c67-41a245707d8c => Stopped>: Remote error: DBConnectionError (_mysql_exceptions.OperationalError) (2013, "Lost connection to MySQL server at 'reading initial communication packet', system error: 11")

And, as a result, Nova crashed right after it:
2016-09-13T01:30:08.401516+00:00 err: 2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db [-] Unexpected error while reporting service status
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db Traceback (most recent call last):
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/nova/servicegroup/drivers/db.py", line 89, in _report_state
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db service.service_ref.save()
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/oslo_versionedobjects/base.py", line 210, in wrapper
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db ctxt, self, fn.__name__, args, kwargs)
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/nova/conductor/rpcapi.py", line 241, in object_action
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db objmethod=objmethod, args=args, kwargs=kwargs)
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", line 169, in call
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db retry=self.retry)
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/oslo_messaging/transport.py", line 96, in _send
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db timeout=timeout, retry=retry)
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 464, in send
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db retry=retry)
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db File "/usr/lib/python2.7/dist-packages/oslo_messaging/_drivers/amqpdriver.py", line 455, in _send
2016-09-13 01:30:08.400 9013 ERROR nova.servicegroup.drivers.db raise result

So, there is a problem with MySQL instance.

[Stanislaw Bogatkin (sbogatkin)]

Seems that problem doesn't depend on commit - there is the same bug with another build:
https://ci.fuel-infra.org/job/master.fuel-library.pkgs.ubuntu.smoke_neutron/7704/

[Maksim Malchuk (mmalchuk)]

node-2.test.domain.local/puppet-apply.log

2016-09-13T00:55:24.523137+00:00 notice: (/Stage[main]/Cluster::Rabbitmq_fence/Exec[enable_corosync_notifyd]/returns) sed: can't read /etc/default/corosync-notifyd: No such file or directory
2016-09-13T00:55:24.523390+00:00 err: sed -i s/START=no/START=yes/ /etc/default/corosync-notifyd returned 2 instead of one of [0]

this is duplicate for https://bugs.launchpad.net/fuel/+bug/1622590