Unable to establish tunnel across hypervisor

Bug #1507684 reported by Romil Gupta
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Romil Gupta

Bug Description

As part of networking-vsphere project which runs ovsvapp agent
on each ESXi host inside service VM, which talk to neutron-server
having l2pop enabled in a multi-hypervisor mode like KVM, ESXi.
The tunnels are not getting established between KVM compute node
and ESXi host. The l2pop mech_driver needs to embrace ovsvapp agent
to form the tunnels.

Romil Gupta (romilg)
Changed in neutron:
assignee: nobody → Romil Gupta (romilg)
Changed in neutron:
status: New → In Progress
Ryan Moats (rmoats)
tags: added: rfe
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

No RFE, simple bug, IMO

Changed in neutron:
importance: Undecided → Medium
tags: added: rfe-approved
removed: rfe
tags: added: l2-pop
removed: rfe-approved
Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/236970
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=07aa19b2236976229971b13e9ece80b862d298b2
Submitter: Jenkins
Branch: master

commit 07aa19b2236976229971b13e9ece80b862d298b2
Author: Romil Gupta <email address hidden>
Date: Mon Oct 19 06:17:04 2015 -0700

    Remove SUPPORTED_AGENT_TYPES for l2pop

    In a world where agents can be out of tree,
    this check seems no longer necessary.

    As part of networking-vsphere project which runs ovsvapp agent
    on each ESXi host inside service VM, which talk to neutron-server
    having l2pop enabled in a multi-hypervisor mode like KVM, ESXi.
    The tunnels are not getting established between KVM compute node
    and ESXi host. The l2pop mech_driver needs to embrace ovsvapp agent
    to form the tunnels.

    Hence, this patch-set addresses the issue by removing the
    SUPPORTED_AGENT_TYPES for l2pop.

    Closes-Bug: #1507684
    Change-Id: I93ca5736e4aad41b851d2b7b082b4bb69d1632fb

Changed in neutron:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/liberty)

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/237888

tags: added: liberty-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/liberty)

Reviewed: https://review.openstack.org/237888
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9d40fe1694f1828b8bfa734a906b31c023c845fe
Submitter: Jenkins
Branch: stable/liberty

commit 9d40fe1694f1828b8bfa734a906b31c023c845fe
Author: Romil Gupta <email address hidden>
Date: Mon Oct 19 06:17:04 2015 -0700

    Remove SUPPORTED_AGENT_TYPES for l2pop

    In a world where agents can be out of tree,
    this check seems no longer necessary.

    As part of networking-vsphere project which runs ovsvapp agent
    on each ESXi host inside service VM, which talk to neutron-server
    having l2pop enabled in a multi-hypervisor mode like KVM, ESXi.
    The tunnels are not getting established between KVM compute node
    and ESXi host. The l2pop mech_driver needs to embrace ovsvapp agent
    to form the tunnels.

    Hence, this patch-set addresses the issue by removing the
    SUPPORTED_AGENT_TYPES for l2pop.

    (Cherry-picked from commit 07aa19b2236976229971b13e9ece80b862d298b2)

    Closes-Bug: #1507684
    Change-Id: I93ca5736e4aad41b851d2b7b082b4bb69d1632fb

tags: added: in-stable-liberty
tags: removed: liberty-backport-potential
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/neutron 8.0.0.0b1

This issue was fixed in the openstack/neutron 8.0.0.0b1 development milestone.

Changed in neutron:
status: Fix Committed → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/neutron 7.0.1

This issue was fixed in the openstack/neutron 7.0.1 release.

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.