Bug 2232472 - Check NeutronNetworkType whether the capsule protocol in OVNEncapType is surely included.
Summary: Check NeutronNetworkType whether the capsule protocol in OVNEncapType is sure...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 04:33 UTC by Keigo Noha
Modified: 2023-08-17 07:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Keigo Noha 2023-08-17 04:33:09 UTC 
Description of problem:
Currently, T-H-T has the following parameters.

NeutronNetworkType: Notify neutron what network types can be used for tenant network.
OVNEncapType: Assign a capsule protocol for OVN, geneve or vxlan.

There is no mechanism to ensure that the capsule protocol assigned by OVNEncapType is included in NeutronNetworkType.
Due to that, there is a possibility that geneve is not assigned in NeutronNetworkType.
Then, at the time of tenant network creation, user may find the provider:network_type becomes vxlan.
Finally, this misconfiguration causes network connectivity issue by wrong MTU calculation based on provider:network_type in Neutron.

We should have a check mechanism to confirm NeutronNetworkType parameter includes the protocol assigned by OVNEncapType.
Note You need to log in before you can comment on or make changes to this bug.