external connectivity to floating ip does not work when external-ids:ovn-cms-options="enable-chassis-as-gw" not set

Bug #1848757 reported by Frode Nordahl
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-ovn-chassis
Fix Released
Undecided
Frode Nordahl

Bug Description

The release notes [0] for the ``enable-chassis-as-gw`` states that the feature is optional and that if no chassis has the flag set a chassis with appropriate bridge mappings will be selected.

This works almost as advertised and connectivity from an instance out to the external network works, I can also confirm that when I add a floating IP the source address traffic flowing out from an instance changes to the floating IP.

However, traffic initiated from the external network to the floating ip destined for the instance is not forwarded.

Adding the ``external-ids:ovn-cms-options="enable-chassis-as-gw"`` to the gateway and then re-creating network resources and instance resolves the issue.

I'll try to dig for what exactly is going wrong, it's probably just one check that assumes the enable-chassis-as-gw flag is required when it in reality is not.

0: https://github.com/openstack/networking-ovn/blob/93834508d1795846ffcda2cc179e8b02ebc8ce85/releasenotes/notes/ovn-cms-options-enable-chassis-as-gw-3adc7024478e3efa.yaml

Frode Nordahl (fnordahl)
Changed in charm-ovn-chassis:
status: New → In Progress
assignee: nobody → Frode Nordahl (fnordahl)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to charm-ovn-chassis (master)

Fix proposed to branch: master
Review: https://review.opendev.org/689543

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to charm-ovn-chassis (master)

Reviewed: https://review.opendev.org/689543
Committed: https://git.openstack.org/cgit/x/charm-ovn-chassis/commit/?id=11cd22dac5c474d1323f2effdeddb1d2aa5325ae
Submitter: Zuul
Branch: master

commit 11cd22dac5c474d1323f2effdeddb1d2aa5325ae
Author: Frode Nordahl <email address hidden>
Date: Fri Oct 18 18:26:50 2019 +0200

    workaround: Set ovn-cms-options when valid bridge-mappings

    Change-Id: I7536b4c7ce95613253ac7810cac4744afb45f8a1
    Closes-Bug: #1848757

Changed in charm-ovn-chassis:
status: In Progress → Fix Committed
David Ames (thedac)
Changed in charm-ovn-chassis:
milestone: none → 19.10
David Ames (thedac)
Changed in charm-ovn-chassis:
status: Fix Committed → Fix Released
Revision history for this message
Frode Nordahl (fnordahl) wrote :

Note that this was most likely a side effect of bug 1906922 and I find no evidence of this issue anymore.

The implicit addition of external-ids:ovn-cms-options="enable-chassis-as-gw" will be removed so that we can put the power back to the user to influence preferred locations for GWs without building unit specific bridge-interface-mappings.

no longer affects: networking-ovn
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to charm-ovn-chassis (master)

Reviewed: https://review.opendev.org/c/x/charm-ovn-chassis/+/799674
Committed: https://opendev.org/x/charm-ovn-chassis/commit/857fa870246165ce93088688bb8a8f877ccfaaf5
Submitter: "Zuul (22348)"
Branch: master

commit 857fa870246165ce93088688bb8a8f877ccfaaf5
Author: Frode Nordahl <email address hidden>
Date: Tue Jul 6 15:43:22 2021 +0200

    Add prefer-chassis-as-gw configuration option

    By default the CMS will schedule HA chassis groups across all
    chassis with bridge- and bridge interface mappings configured.

    This configuration option would allow you to influence where
    gateways are scheduled when all units have equal bridge- and
    bridge interface mapping configuration.

    Func-Test-Pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/599
    Closes-Bug: #1908377
    Closes-Bug: #1934678
    Related-Bug: #1848757
    Change-Id: I52f37a512fccbb3a025ffef81fcecb69fa169792

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.