Unable to assign interface to server in vCenter AZ

[Vasily Gorin]

Fuel 8.0 with MU update . VMware DVS Plugin v2.1.0 build #674

Steps to reproduce:
     1. Setup for system tests.
     2. Log in to Horizon Dashboard.
     3. Add two private networks (net01, and net02).
     4. Add one subnet (net01_subnet01: 192.168.101.0/24, net02_subnet01, 192.168.102.0/24) to each network.
     5. Launch instance VM_1 with image TestVM and flavor m1.micro in nova availability zone.
     6. Launch instance VM_2 with image TestVM-VMDK and flavor m1.micro vcenter availability zone.
     7. Check abilities to assign multiple vNIC net01 and net02 to VM_1.
     8. Check abilities to assign multiple vNIC net01 and net02 to VM_2.

Expected result(step-8):
Interfaces were assigned on VM_2

Actual result:
In UI we got message "Unable to assign interface"

In CLI we got message:

root@node-3:~# nova interface-attach --net-id 08f64395-24ff-42e8-bc09-62443be98c85 7b863f90-5868-4598-8e93-1d560b0f47d7
ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
<class 'PortBindingFailed_Remote'> (HTTP 500) (Request-ID: req-8832a3e6-6c95-4112-94d7-41516d330d4f)
root@node-3:~#

Related nova-api log : http://paste.openstack.org/show/520569/

[Vyacheslav Tabolin (slavchick)]

Can not reproduce for VLAN type networks.
Please give us neutron server log for more info.