VM goes in error state if created after ovsvapp restart

[Aman Kumar]

VMs go in error state if VMs are created after ovsvapp restart
1.In Automation test suite many tests have failed due to VMs going in error state .
Below sequence of event happens .
1.Create network and boot vm in that . this works fine .
2.Delete VMs
2. Now Restart ovsvapp agents , and restarting ovsvapp deletes the portgroup
3. Boot VM in same network , it fails to boot . It goes in error state because portgroup does not get created.

[OpenStack Infra (hudson-openstack)]

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

commit fa858c98ba5d3c3166023865bdfc102e1631b565
Author: Aman Kumar <email address hidden>
Date: Thu Mar 23 03:02:03 2017 -0700

    VM goes in error state if created after ovsvapp restart

    VMs are going into error state because the lvid entries
    are not cleared in all the ovsvapp agents when we delete
    all the vms from vcenter and restarting one of the
    ovsvapp-agent from a cluster. So this patch of code
    deletes the port-group when the network_port_count
    becomes zero and informs all the agents in a cluster
    by updating the lvid.

    Closes-Bug: #1679909
    Co-Authored-By: Priyanka J <email address hidden>

    Change-Id: I0d1786ed3256b436ee9d3021a52f25b5f1e65d09

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/453465

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/453512

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/453512
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=ee9fe812bb99af7c5bf7270be25a2717f7bb1ebc
Submitter: Jenkins
Branch: stable/mitaka

commit ee9fe812bb99af7c5bf7270be25a2717f7bb1ebc
Author: Aman Kumar <email address hidden>
Date: Thu Mar 23 03:02:03 2017 -0700

    VM goes in error state if created after ovsvapp restart

    VMs are going into error state because the lvid entries
    are not cleared in all the ovsvapp agents when we delete
    all the vms from vcenter and restarting one of the
    ovsvapp-agent from a cluster. So this patch of code
    deletes the port-group when the network_port_count
    becomes zero and informs all the agents in a cluster
    by updating the lvid.

    Closes-Bug: #1679909
    Co-Authored-By: Priyanka J <email address hidden>

    (cherry picked from commit fa858c98ba5d3c3166023865bdfc102e1631b565)

    Conflicts:
     networking_vsphere/ml2/ovsvapp_mech_driver.py

    Change-Id: I0d1786ed3256b436ee9d3021a52f25b5f1e65d09

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/453465
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=bcff8e5b9f06780b6964980d1b1f911ceada2198
Submitter: Jenkins
Branch: stable/ocata

commit bcff8e5b9f06780b6964980d1b1f911ceada2198
Author: Aman Kumar <email address hidden>
Date: Thu Mar 23 03:02:03 2017 -0700

    VM goes in error state if created after ovsvapp restart

    VMs are going into error state because the lvid entries
    are not cleared in all the ovsvapp agents when we delete
    all the vms from vcenter and restarting one of the
    ovsvapp-agent from a cluster. So this patch of code
    deletes the port-group when the network_port_count
    becomes zero and informs all the agents in a cluster
    by updating the lvid.

    Also changed the typo in tox.ini file

    Closes-Bug: #1679909
    Co-Authored-By: Priyanka J <email address hidden>

    Change-Id: I0d1786ed3256b436ee9d3021a52f25b5f1e65d09
    (cherry picked from commit fa858c98ba5d3c3166023865bdfc102e1631b565)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/459948

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/459948
Committed: https://git.openstack.org/cgit/openstack/networking-vsphere/commit/?id=7ee41fe55d9b536d63c2cd1b53cf2c758a42d059
Submitter: Jenkins
Branch: stable/newton

commit 7ee41fe55d9b536d63c2cd1b53cf2c758a42d059
Author: Aman Kumar <email address hidden>
Date: Thu Mar 23 03:02:03 2017 -0700

    VM goes in error state if created after ovsvapp restart

    VMs are going into error state because the lvid entries
    are not cleared in all the ovsvapp agents when we delete
    all the vms from vcenter and restarting one of the
    ovsvapp-agent from a cluster. So this patch of code
    deletes the port-group when the network_port_count
    becomes zero and informs all the agents in a cluster
    by updating the lvid.

    Closes-Bug: #1679909
    Co-Authored-By: Priyanka J <email address hidden>

    (cherry picked from commit fa858c98ba5d3c3166023865bdfc102e1631b565)

    Conflicts:
     networking_vsphere/ml2/ovsvapp_mech_driver.py

    Change-Id: I0d1786ed3256b436ee9d3021a52f25b5f1e65d09