when VM is booted with multiple nics (two in this case) one of the nic fails to get ip

[Romil Gupta]

1.create 2 networks
2. host a dual nic VM with these two nics (this is the first VM for these networks)
3. we see that one of the nic fails to get ip.

This problem applies for both VLAN and VXLAN scenarios. This problem occurs due to timing issues between the SG provider rule update and OVS Firewall based filtered port population via device_create RPC, which misses the existence of SG provider rule on br-sec.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/226695

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/226695
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=a64d1ae60694cddb095239bd3539ad1c0cb3dc67
Submitter: Jenkins
Branch: master

commit a64d1ae60694cddb095239bd3539ad1c0cb3dc67
Author: Romil Gupta <email address hidden>
Date: Wed Sep 23 03:56:30 2015 -0700

    Fix for VM with 2 nics: 1 nic not getting IP

    When a VM is spawned with 2 nics, second nic was not getting
    IP and the sg provider rule was missing on br-sec - table=0.
    This was due to enhanced sg provider rule RPC missing to process
    since the port is not yet filled in filtered_ports list in
    OVS firewall. Also, sg_rules obtained from get_ports_for_device
    RPC was missing sg provider rule in it. Resolved these timings
    issues in this patch set.

    Change-Id: Idb46b545ac768f193160328f376e32934b3c58c2
    Co-Authored-By: Rashmi P <email address hidden>
    Closes-Bug: #1494694