neutron

[ovn-octavia-provider] ovn-lb with VIP on provider network not working

Bug #2003997 reported by Luis Tomas Bolivar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Luis Tomas Bolivar

Bug Description

In core OVN, LBs on switches with localnet ports (i.e., neutron
provider networks) don't work if traffic comes from localnet [1]

In order to force NAT to happen at the virtual router instead
of the LS level, when the VIP of the LoadBalancer is associated
to a provider network we should avoid adding the LB to the
LS associated to the provider network

Luis Tomas Bolivar (ltomasbo)
Changed in neutron:
assignee: nobody → Luis Tomas Bolivar (ltomasbo)
OpenStack Infra (hudson-openstack)
Changed in neutron:
status: New → In Progress
Oleg Bondarev (obondarev)
tags: added: ovn-octavia-provider
Changed in neutron:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (master)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/871263
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/d10feb642f2adacb90c83e383fd387e8f4e87295
Submitter: "Zuul (22348)"
Branch: master

commit d10feb642f2adacb90c83e383fd387e8f4e87295
Author: Luis Tomas Bolivar <email address hidden>
Date: Thu Jan 26 17:04:55 2023 +0100

    Remove LB from LS belonging to provider networks

    In core OVN, LBs on switches with localnet ports (i.e., neutron
    provider networks) don't work if traffic comes from localnet [1]

    In order to force NAT to happen at the virtual router instead
    of the LS level, when the VIP of the LoadBalancer is associated
    to a provider network we should avoid adding the LB to the
    LS associated to the provider network

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=2164652

    Closes-Bug: #2003997

    Change-Id: I009ddd2604d208bbf793e2d19d4195b77726f7b2

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ovn-octavia-provider (stable/zed)

Fix proposed to branch: stable/zed
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872577

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ovn-octavia-provider (stable/yoga)

Fix proposed to branch: stable/yoga
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872578

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ovn-octavia-provider (stable/xena)

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872579

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ovn-octavia-provider (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872580

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (stable/xena)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872579
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/d989216e36c05f00fa514cc6f0901df7e71cf289
Submitter: "Zuul (22348)"
Branch: stable/xena

commit d989216e36c05f00fa514cc6f0901df7e71cf289
Author: Luis Tomas Bolivar <email address hidden>
Date: Thu Jan 26 17:04:55 2023 +0100

    Remove LB from LS belonging to provider networks

    In core OVN, LBs on switches with localnet ports (i.e., neutron
    provider networks) don't work if traffic comes from localnet [1]

    In order to force NAT to happen at the virtual router instead
    of the LS level, when the VIP of the LoadBalancer is associated
    to a provider network we should avoid adding the LB to the
    LS associated to the provider network

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=2164652

    Closes-Bug: #2003997

    Change-Id: I009ddd2604d208bbf793e2d19d4195b77726f7b2
    (cherry picked from commit d10feb642f2adacb90c83e383fd387e8f4e87295)

tags: added: in-stable-xena
tags: added: in-stable-wallaby
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872580
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/ea6efa9b7bd476629037bd92918ad0669c518795
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit ea6efa9b7bd476629037bd92918ad0669c518795
Author: Luis Tomas Bolivar <email address hidden>
Date: Thu Jan 26 17:04:55 2023 +0100

    Remove LB from LS belonging to provider networks

    In core OVN, LBs on switches with localnet ports (i.e., neutron
    provider networks) don't work if traffic comes from localnet [1]

    In order to force NAT to happen at the virtual router instead
    of the LS level, when the VIP of the LoadBalancer is associated
    to a provider network we should avoid adding the LB to the
    LS associated to the provider network

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=2164652

    Closes-Bug: #2003997

    Change-Id: I009ddd2604d208bbf793e2d19d4195b77726f7b2
    (cherry picked from commit d10feb642f2adacb90c83e383fd387e8f4e87295)

tags: added: in-stable-zed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (stable/zed)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872577
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/0841ec815e9587bfd1c91313538118fb550d7b41
Submitter: "Zuul (22348)"
Branch: stable/zed

commit 0841ec815e9587bfd1c91313538118fb550d7b41
Author: Luis Tomas Bolivar <email address hidden>
Date: Thu Jan 26 17:04:55 2023 +0100

    Remove LB from LS belonging to provider networks

    In core OVN, LBs on switches with localnet ports (i.e., neutron
    provider networks) don't work if traffic comes from localnet [1]

    In order to force NAT to happen at the virtual router instead
    of the LS level, when the VIP of the LoadBalancer is associated
    to a provider network we should avoid adding the LB to the
    LS associated to the provider network

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=2164652

    Closes-Bug: #2003997

    Change-Id: I009ddd2604d208bbf793e2d19d4195b77726f7b2
    (cherry picked from commit d10feb642f2adacb90c83e383fd387e8f4e87295)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to ovn-octavia-provider (stable/yoga)

Reviewed: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/872578
Committed: https://opendev.org/openstack/ovn-octavia-provider/commit/a0d855a743181c72830766a41bda04f45c78bca3
Submitter: "Zuul (22348)"
Branch: stable/yoga

commit a0d855a743181c72830766a41bda04f45c78bca3
Author: Luis Tomas Bolivar <email address hidden>
Date: Thu Jan 26 17:04:55 2023 +0100

    Remove LB from LS belonging to provider networks

    In core OVN, LBs on switches with localnet ports (i.e., neutron
    provider networks) don't work if traffic comes from localnet [1]

    In order to force NAT to happen at the virtual router instead
    of the LS level, when the VIP of the LoadBalancer is associated
    to a provider network we should avoid adding the LB to the
    LS associated to the provider network

    [1] https://bugzilla.redhat.com/show_bug.cgi?id=2164652

    Closes-Bug: #2003997

    Change-Id: I009ddd2604d208bbf793e2d19d4195b77726f7b2
    (cherry picked from commit d10feb642f2adacb90c83e383fd387e8f4e87295)

tags: added: in-stable-yoga
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ovn-octavia-provider 4.0.0.0rc1

This issue was fixed in the openstack/ovn-octavia-provider 4.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ovn-octavia-provider 1.3.0

This issue was fixed in the openstack/ovn-octavia-provider 1.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ovn-octavia-provider 2.1.0

This issue was fixed in the openstack/ovn-octavia-provider 2.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ovn-octavia-provider 3.1.0

This issue was fixed in the openstack/ovn-octavia-provider 3.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/ovn-octavia-provider wallaby-eom

This issue was fixed in the openstack/ovn-octavia-provider wallaby-eom release.

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

Other bug subscribers

Remote bug watches

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