Tenant VMs lose connectivity for more than 4 Mins during vmotion

Bug #1681792 reported by Priyanka J
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-vsphere
Fix Released
Undecided
Priyanka J

Bug Description

Ping should recover with few secs after vmotion/migration, but here it losts for more than 4 mins and recovers after that.

This bug is blocker to validate ovsvapp sanity testcases for Vmotion.

Sequence to recreate this bug,

1. Deploy CS 10.1 with ESX computes in VLAN environment .
2. Create a VM in VLAN network
3. Assign FIP to the VM
4. Add a ICMP rule to allow ping traffic
5. Ping the VM using FIP , its successful .
6. Now Migrate the VM to another host
7. Ping connectivity of the VM is lost for more than 4 Mins.

Priyanka J (priyaj)
Changed in networking-vsphere:
assignee: nobody → Priyanka J (priyaj)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-vsphere (master)

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

Changed in networking-vsphere:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-vsphere (master)

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

commit e74556bddb77b0e36cd4757429b68e7e99a40979
Author: PriyankaJ <email address hidden>
Date: Tue Apr 11 04:10:03 2017 -0700

    CLDSYS-17372 Tenant VMs lose connectivity for more than 4 Mins during vmotion.

    This patch recovers the connectivity of Tenant VMs within few
    seconds after vmotion as expected.

    Closes-Bug: #1681792
    Change-Id: Ic50f0e012a42061424388acf40eb286fe498eda9

Changed in networking-vsphere:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-vsphere (stable/mitaka)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-vsphere (stable/ocata)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-vsphere (stable/newton)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-vsphere (stable/mitaka)

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

commit 0ecb9b3af5e3af132ff1d59f96c579c2c09d2aee
Author: PriyankaJ <email address hidden>
Date: Tue Apr 11 04:10:03 2017 -0700

    Tenant VMs lose connectivity for more than 4 Mins during vmotion.

    This patch recovers the connectivity of Tenant VMs within few
    seconds after vmotion as expected.

    Closes-Bug: #1681792
    Change-Id: Ic50f0e012a42061424388acf40eb286fe498eda9
    (cherry picked from commit e74556bddb77b0e36cd4757429b68e7e99a40979)

tags: added: in-stable-mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-vsphere (stable/newton)

Change abandoned by Tony Breeds (<email address hidden>) on branch: stable/newton
Review: https://review.openstack.org/459951
Reason: This branch (stable/newton) is at End Of Life

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.