Deployment process of openstack on the second controller of nsx's machine always fails due to different reasons.

I've checked this bug on different configurations of env in ha mode.
After each fallen deploy I've reseted snapshot on nsx machine and cleared previous envs.

==============nsx settings===========================
Fuel UI-> Settings -> VMware NSX

NSX_USERNAME='admin'
NSX_PASSWORD= 'admin'
NSX_TRANSPORT_ZONE='0f12c1f7-5605-46b6-aa3f-4bf50bde47e5'
L3_SERVICE_UUID='aa153851-bd8e-4852-9772-d98a431849e0'
NSX_CONTROLLER_ENDPOINT='172.16.1.253'
URL_TO_NSX_BITS='http://10.20.204.1'

NSX network -> management -> untag and set 172.16.1.0/24 on eth2
=====================================================
Configuration 1:
===================================================
steps to reproduce:
1.set up lab on nsx machine
2.create env and start deploy:
   OS: Ubuntu (HA mode)
   hypervisor: QEMU
   roles: 3 controllers, 1 compute, 1 cinder

3. check that deployment of openstack on 1st controller is finished successfully
4. check that deployment of openstack on 2nd controller is failed

Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result: deployment of openstack on 2nd controller is failed due to reason: Could not find init script or upstart conf file for 'glance-registry'

------------Logs------------------------------------

root@node-12:~# less /var/log/puppet.log

Thu Sep 11 19:45:49 +0000 2014 /Stage[main]/Glance::Registry/Service[glance-registry] (notice): Dependency Service[mysql-service] has failure
s: true
Thu Sep 11 19:45:49 +0000 2014 /Stage[main]/Glance::Registry/Service[glance-registry] (warning): Skipping because of failed dependencies
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry.conf in /etc/init
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry.conf in /etc/init.d
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry in /etc/init
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry in /etc/init.d
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry.sh in /etc/init
Thu Sep 11 19:45:49 +0000 2014 Service[glance-registry](provider=upstart) (debug): Could not find glance-registry.sh in /etc/init.d
Thu Sep 11 19:45:49 +0000 2014 /Stage[main]/Glance::Registry/Service[glance-registry] (err): Failed to call refresh: Could not find init script or upstart conf file for 'glance-registry'
Thu Sep 11 19:45:49 +0000 2014 /Stage[main]/Glance::Registry/Service[glance-registry] (err): Could not find init script or upstart conf file for 'glance-registry'

Glance package is not installed due to some reason.

root@node-12:~# aptitude show glance-registry
Package: glance-registry
State: not installed
Version: 1:2014.1.1-fuel5.1~mira10
Priority: extra
Section: python
Maintainer: Ubuntu OpenStack <email address hidden>
Architecture: all
Uncompressed Size: 21.5 k
Depends: glance-common (= 1:2014.1.1-fuel5.1~mira10), upstart-job, python
Recommends: python-glanceclient
Replaces: glance (< 2012.1~e1~20110919.1021-0ubuntu2), glance (< 2012.1~e1~20110919.1021-0ubuntu2)
Description: OpenStack Image Registry and Delivery Service - Registry
 The Glance project provides an image registration, discovery and delivery service. These services may be used as stand-along services, and
 they may also be used by Nova to deliver images from object stores, such as OpenStack's Swift service, to Nova's compute nodes.

 This package contains the glance registry server.
Homepage: http://launchpad.net/glance

=================================================
Configuration 2:
=================================================
steps to reproduce:
1.set up lab on nsx machine
2.create env and start deploy:
   OS: Ubuntu (HA mode)
   hypervisor: QEMU
   roles: 2 controllers, 1 compute

3. check that deployment of openstack on 1st controller is finished successfully
4. check that deployment of openstack on 2nd controller is failed

Expected result: Deployment process of openstack on each of nodes will be finished successfully
Actual result:deployment of openstack on 2nd controller is failed due to reason: MySQL is not running

-----------------Logs------------------------------------
Trace from HC logs on node-7 (controller) (/Stage[main]/Galera/Service[mysql-service]/ensure) change from stopped to running failed: execution expired

Trace from node-7 : less /var/log less mysqld.log
<30>Sep 11 14:25:17 node-7 mysql-wss[2680]: INFO: PIDFile /var/run/mysqld/mysqld.pid of MySQL server not found. Sleeping for 5 seconds. 0 retries left
<30>Sep 11 14:25:22 node-7 mysql-wss[2680]: INFO: MySQL is not running
<27>Sep 11 14:25:22 node-7 mysql-wss[2680]: ERROR: GTID have wrong format: :
<27>Sep 11 14:25:22 node-7 mysql-wss[2680]: ERROR: Wrong GTID, not updating gtid attribute
<30>Sep 11 14:25:22 node-7 mysql-wss[2680]: INFO: PIDFile /var/run/mysqld/mysqld.pid of MySQL server not found. Sleeping for 5 seconds. 2 retries left
<30>Sep 11 14:25:27 node-7 mysql-wss[2680]: INFO: PIDFile /var/run/mysqld/mysqld.pid of MySQL server not found. Sleeping for 5 seconds. 1 retries left
<30>Sep 11 14:25:32 node-7 mysql-wss[2680]: INFO: PIDFile /var/run/mysqld/mysqld.pid of MySQL server not found. Sleeping for 5 seconds. 0 retries left
<30>Sep 11 14:25:37 node-7 mysql-wss[2680]: INFO: MySQL is not running
<30>Sep 11 14:25:37 node-7 mysql-wss[2913]: INFO: PIDFile /var/run/mysqld/mysqld.pid of MySQL server not found. Sleeping for 5 seconds. 0 retries left
<30>Sep 11 14:25:42 node-7 mysql-wss[2913]: INFO: MySQL is not running
<27>Sep 11 14:25:42 node-7 mysql-wss[2913]: ERROR: Directory /var/run/mysqld is not writable by mysql
<30>Sep 11 14:25:42 node-7 mysql-wss[2976]: INFO: MySQL is not running

no one service not available on node-7

and after manually restart and stop of mysql service too.