What is the process or dependencies by which OVN determines a logical routers interface(s) to be in a "ACTIVE" or "DOWN" state and notify Neutron of that status upstream? I read https://docs.openstack.org/networking-ovn/ocata/design/ovn_worker.html document, but it seems to refer to virtual machines that are created/destroyed and I am unsure if the same applies to logical routers. I have seen now on several occasions where OVN will report a network port as down for no reason then up then back down similar to a traditional network link flap, but ultimately the port remains in a down state (example below) and can find now way to bring the port online.

In troubleshooting this issue I can find/see no obvious errors in the logs for OVS, OVN, or Neutron, and this does not occur with instance ports, all of the patch ports on the compute node appear to be in place, and the integration bridge (br-int) is up and running (two instances on the same subnet are able to communicate). This is on Ocata release, CentOS 7, OVS/OVN 2.6.1 from package not source.

cat /var/log/neutron/server.log | grep "networking_ovn.ml2.mech_driver" | awk '{ print $1=$2=""; print $0}' 5393 INFO networking_ovn.ml2.mech_driver [req-d4aa53c5-b78e-4360-9c9e-194f76cdb15c - - - - -] Starting OVNMechanismDriver 5416 INFO networking_ovn.ml2.mech_driver [-] OVN reports status up for port: 90b16a19-11d9-4844-8fbe-2340367f18d5 5416 INFO networking_ovn.ml2.mech_driver [req-347dbab3-4326-4a0d-b77c-eccc5532bee1 - - - - -] OVN reports status down for port: 90b16a19-11d9-4844-8fbe-2340367f18d5 5416 INFO networking_ovn.ml2.mech_driver [req-347dbab3-4326-4a0d-b77c-eccc5532bee1 - - - - -] OVN reports status up for port: 90b16a19-11d9-4844-8fbe-2340367f18d5 5416 INFO networking_ovn.ml2.mech_driver [req-347dbab3-4326-4a0d-b77c-eccc5532bee1 - - - - -] OVN reports status down for port: 90b16a19-11d9-4844-8fbe-2340367f18d55

openstack port list
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+
| ID | Name | MAC Address | Fixed IP Addresses | Status |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+
| 90b16a19-11d9-4844-8fbe-2340367f18d5 | | fa:16:3e:b6:bd:29 | ip_address='172.18.0.1', subnet_id='8bfc9808-ba56-49ce-b308-ed6d7f1c6701' | DOWN |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------+--------+

openstack router list
+--------------------------------------+-------------------+--------+-------+-------------+-------+----------------------------------+
| ID | Name | Status | State | Distributed | HA | Project |
+--------------------------------------+-------------------+--------+-------+-------------+-------+----------------------------------+
| e2b7766b-2121-4874-babe-080f6ef8ad84 | router-internal-1 | ACTIVE | UP | False | False | 6cde3f9359c84acdb6ae916d438045bf |
+--------------------------------------+-------------------+--------+-------+-------------+-------+----------------------------------+

Cheers,

-C
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to