Fuel duplicates the TestVM image in glance+vCenter configuration

[okosse]

When deployment an environment in mode multi-node with HA, in the glance there are two image TestVM. They are available in the horizon and visible in the vCenter.

==============vcenter settings===========================
export VCENTER_IP='172.16.0.254'
export <email address hidden>'
export VCENTER_PASSWORD='Qwer!1234'
export VCENTER_CLUSTERS='Cluster1,Cluster2'
=====================================================
Configuration:
===================================================
steps to reproduce:
1.set up lab from fuel-6.0-icehouse-13-2014-10-14_00-01-06.iso
2.create env and start deploy:
   OS: CentOS ( multi-node with HA)
   glance: VMWare vCenter/ESXi
   create nodes with roles: 3st - controller
3. start deployment

---------------------fuel-version---------------------------------
api: '1.0'
astute_sha: a3e5da62af91b99f958ab958161d3dcec09c657b
auth_required: true
build_id: 2014-09-18_01-09-23
build_number: '514'
feature_groups:
- mirantis
fuellib_sha: ac4e608e259cb651793561918e4bd955a5d3643a
fuelmain_sha: 9a52633718c1937ef4d0cb244b78e3a14f4d0bd5
nailgun_sha: 72d0294e92b044dee8e45f050df61a4b864ea96a
ostf_sha: dd546af672de75fb23873fa9ed31d29b70215f55
production: docker
release: '6.0'
release_versions:
  2014.1.1-5.1:
    VERSION:
      api: '1.0'
      astute_sha: a3e5da62af91b99f958ab958161d3dcec09c657b
      build_id: 2014-09-18_01-09-23
      build_number: '514'
      feature_groups:
      - mirantis
      fuellib_sha: ac4e608e259cb651793561918e4bd955a5d3643a
      fuelmain_sha: 9a52633718c1937ef4d0cb244b78e3a14f4d0bd5
      nailgun_sha: 72d0294e92b044dee8e45f050df61a4b864ea96a
      ostf_sha: dd546af672de75fb23873fa9ed31d29b70215f55
      production: docker
      release: '6.0'

[Nastya Urlapova (aurlapova)]

Please investigate, at first glance is dublicate https://bugs.launchpad.net/fuel/+bug/1342039

[Oleksandr Martsyniuk (omartsyniuk)]

Could not reproduce with fuel-6.0-56-2014-12-18_01-32-01.iso

[Stanislaw Bogatkin (sbogatkin)]

This bug was incomplete for more than 4 weeks. We cannot investigate it further so we are setting the status to Invalid. If you think it is not correct, please feel free to provide requested information and reopen the bug, and we will look into it further.