+ exec neutron-ovn-vpn-agent --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/neutron_vpnaas.conf --config-file /etc/neutron/neutron_ovn_vpn_agent.ini --config-file /tmp/pod-shared/neutron-agent.ini --config-file /tmp/pod-shared/ovn.ini
This program is using eventlet and has been monkey_patched
2026-02-27 19:44:04.284 186 INFO neutron.common.config [-] Logging enabled!
2026-02-27 19:44:04.284 186 INFO neutron.common.config [-] /var/lib/openstack/bin/neutron-ovn-vpn-agent version 27.0.0
2026-02-27 19:44:04.285 186 WARNING stevedore.named [-] Could not load neutron_vpnaas.services.vpn.device_drivers.ovn_ipsec.OvnStrongSwanDriver
2026-02-27 19:44:04.401 186 WARNING oslo_config.cfg [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] Deprecated: Option "ovn_emit_need_to_frag" from group "ovn" is deprecated for removal (The option is useful only on very old Linux kernels (version < 5.2).).  Its value may be silently ignored in the future.
2026-02-27 19:44:04.428 186 INFO ovsdbapp.backend.ovs_idl.vlog [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] unix:/run/openvswitch/db.sock: connecting...
2026-02-27 19:44:04.429 186 INFO ovsdbapp.backend.ovs_idl.vlog [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] unix:/run/openvswitch/db.sock: connected
2026-02-27 19:44:04.488 186 INFO ovsdbapp.backend.ovs_idl.vlog [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] tcp:10.96.171.117:6642: connecting...
2026-02-27 19:44:04.489 186 INFO ovsdbapp.backend.ovs_idl.vlog [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] tcp:10.96.171.117:6642: connected
2026-02-27 19:54:04.996 186 ERROR neutron_lib.rpc [None req-2f663da6-93ce-4b2b-84b6-76dc834ba165 - - - - - -] Timeout in RPC method get_vpn_services_on_host. Waiting for 426 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 6a96e3a357db49ffb8f40e64afb914fc