Bug 2232472

Summary:	Check NeutronNetworkType whether the capsule protocol in OVNEncapType is surely included.
Product:	Red Hat OpenStack	Reporter:	Keigo Noha <knoha>
Component:	openstack-tripleo-heat-templates	Assignee:	OSP Team <rhos-maint>
Status:	NEW ---	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17.1 (Wallaby)	CC:	bshephar, mburns
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.