vCenter's instances doesn't get network settings

[okosse]

vCenter's instances doesn't get network settings :
Scenario:
1. Deploy cluster in dualhypervisor mode with 1 controller only
2. Run ostf
3. Login in Horizon, create instance and check network connectivity

Expected result: all step pass

actual result:
1. All OSTF tests which contains "Check that public IP 8.8.8.8 can be pinged from instance." failed.
2. Error "Error: Unable to connect to Neutron" popups in horizon
3. vCenter's instances doesn't get network settings

----------------iso version-------------------------------
api: '1.0'
astute_sha: 126709e7f18a719ec4bd2a13a37d972285381892
auth_required: true
build_id: 2015-07-30_03-46-56
build_number: '110'
feature_groups:
- mirantis
fuel-agent_sha: 355c08a04917f047b88f66242767049d2b1d0ff0
fuel-library_sha: 90aff7558fb00373ccd363b7722e2f90dc25894d
fuel-nailgun-agent_sha: 1512b9af6b41cc95c4d891c593aeebe0faca5a63
fuel-ostf_sha: f907eca277ab4ba769774417d6ff5bf30ef479ee
fuelmain_sha: de5b333815f8541224c6726dc8446ffc7fb18b5b
nailgun_sha: 999efffd19b823a27b17f0e97a42ac0d47ae9ce5
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: f04e6c46783ecd6000df31b61b6749da66d4d828
release: '7.0'
release_versions:
  2015.1.0-7.0:
    VERSION:
      api: '1.0'
      astute_sha: 126709e7f18a719ec4bd2a13a37d972285381892
      build_id: 2015-07-30_03-46-56
      build_number: '110'
      feature_groups:
      - mirantis
      fuel-agent_sha: 355c08a04917f047b88f66242767049d2b1d0ff0
      fuel-library_sha: 90aff7558fb00373ccd363b7722e2f90dc25894d
      fuel-nailgun-agent_sha: 1512b9af6b41cc95c4d891c593aeebe0faca5a63
      fuel-ostf_sha: f907eca277ab4ba769774417d6ff5bf30ef479ee
      fuelmain_sha: de5b333815f8541224c6726dc8446ffc7fb18b5b
      nailgun_sha: 999efffd19b823a27b17f0e97a42ac0d47ae9ce5
      openstack_version: 2015.1.0-7.0
      production: docker
      python-fuelclient_sha: f04e6c46783ecd6000df31b61b6749da66d4d828
      release: '7.0'

[Timur Nurlygayanov (tnurlygayanov)]

This bug is blocker for vCenter QA team, could we force the fix or provide some workaround?

[Igor Zinovik (izinovik)]

I analyzed the bug, but still do not determined the root cause of the problem.

In my environment while listening with tcpdump on following interfaces eth3.103 (VM Fixed network),
br100 I was not able to see incoming DHCP requests from VMs started by nova-compute (VCDriver configured).

[Igor Zinovik (izinovik)]

After investigation of vCenter settings I discovered the root cause.

In vCenter there was two port groups both named 'br100'. One was
connected to standard vSwitch (br100 - standard switch network),
second one was connected to distributed vSwitch (br100 - distributed port group).

In nova-network configuration we specify flat_network_bridge which, when vCenter
is used, means that nova-compute (not nova-network!) will provision network port
on this port group.

During VM creation VM ports were provisioned on standard network 'br100' that was
not assigned correct VLAN tag (103).

After removing standard switch network 'br100' VMs were able to get
IP address and connect to to external networks.

Marking as Invalid since this is pure infrastructure problem.