Comment 10 for bug 1394137

When this issue had been reproduced, the mysqld.log contained "[Note] /usr/sbin/mysqld: ready for connections" message with a *later* timestamp than puppet-apply.log contained one for "Exec[wait-for-haproxy-mysql-backend]) Evaluated". That resulted in Openstack services considered wait-for-haproxy-mysql-backend precondition had been met and started to issue connections to mysql which obviously failed due to it wasn't ready for connections yet.

This bug is floating, hence barely reproducible w/o long run testing for looped deployments