Comment 3 for bug 1470568

Able to reproduce it on a multi-node deployment with non-SR-IOV ports
Steps:
1. neutron net-create my-private-network
2. neutron subnet-create --ip_version 4 --gateway 10.0.6.1 --name my-private-subnet my-private-network 10.0.6.0/24
3. Create port1 on a compute1: neutron port-create 5f109df7-e71c-45c2-b3aa-d1e36a69d3d3 --binding:host_id=<hostname of compute1>
4. Create port2 on a compute2: neutron port-create 5f109df7-e71c-45c2-b3aa-d1e36a69d3d3 --binding:host_id=<hostname of compute2>
5. Boot an instance attached to port1
6. Boot an instance attached to port2

Result: VLAN is added to vNICs of an only first compute. The second compute does not have VLAN added to vNICs
Message in q-svc.log:
2015-07-15 08:20:30.368 DEBUG networking_cisco.plugins.ml2.drivers.cisco.ucsm.ucsm_network_driver [req-e62f2942-9150-40fa-b2ea-1f3e98e9e9c2 None None] UCS Manager network driver found an entry that already exists os3 from (pid=35642) update_serviceprofile /usr/local/lib/python2.7/distpackages/networking_cisco/plugins/ml2/drivers/cisco/ucsm/ucsm_network_driver.py:424