[Neurton][OVN] Not able to remove geneve tunnel
As part of openstack-ansible deployment, removed geneve tunnel config as you mentioned, now we have only below on neutron server [ml2] type_drivers = vlan tenant_network_types = vlan mechanism_drivers = ovn Same config for neutron in compute node as well, under ovn external_id external_ids : {hostname=xxxx ovn-bridge-mappings="vlan:br-ex", ovn-cms-options="availability-zones=nova", ovn-remote="tcp:xxxx:6642,tcp:xxxxx:6642", rundir="/var/run/openvswitch", system-id="01a70eda-59bb-4e8b-870d-08eba09abae3"} With above config, we do see below error in ovn-controller & not able to connect to SB DB ovn-controller.log: 2025-04-29T17:38:48.508Z|00012|main|INFO|OVN internal version is : [24.03.2-20.33.0-72.6] 2025-04-29T17:38:55.206Z|00026|chassis|INFO|Need to specify an encap type and ip 2025-04-29T17:38:55.206Z|00027|chassis|INFO|Need to specify an encap type and ip 2025-04-29T17:38:55.206Z|00028|chassis|INFO|Need to specify an encap type and ip can you please share your inputs on this ? Ideally we don't want to have ovn-*** ports to be created
Reference from other thread https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....
Hi, On 4/29/25 6:38 PM, keerthivassan86@gmail.com wrote:
As part of openstack-ansible deployment, removed geneve tunnel config as you mentioned, now we have only below on neutron server
[ml2] type_drivers = vlan tenant_network_types = vlan mechanism_drivers = ovn
Same config for neutron in compute node as well, under ovn external_id
external_ids : {hostname=xxxx ovn-bridge-mappings="vlan:br-ex", ovn-cms-options="availability-zones=nova", ovn-remote="tcp:xxxx:6642,tcp:xxxxx:6642", rundir="/var/run/openvswitch", system-id="01a70eda-59bb-4e8b-870d-08eba09abae3"}
With above config, we do see below error in ovn-controller & not able to connect to SB DB
ovn-controller.log:
2025-04-29T17:38:48.508Z|00012|main|INFO|OVN internal version is : [24.03.2-20.33.0-72.6] 2025-04-29T17:38:55.206Z|00026|chassis|INFO|Need to specify an encap type and ip 2025-04-29T17:38:55.206Z|00027|chassis|INFO|Need to specify an encap type and ip 2025-04-29T17:38:55.206Z|00028|chassis|INFO|Need to specify an encap type and ip
can you please share your inputs on this ? Ideally we don't want to have ovn-*** ports to be created
ovn-controller will not start unless both ovn-encap-type and ovn-encap-ip are set, so you will need to add the geneve type driver config back. As you said in your other email that you don't allow users to create networks this should not be an issue. I guess if you're not using OVN at all and are just using vlan networks you can change to using 'openvswitch' as the mechanism driver? -Brian
participants (2)
-
Brian Haley
-
keerthivassan86@gmail.com