Numan,
If I am following your comment correctly and this is just a lack of
status messaging that does not prevent the gateway from becoming active
(i.e. it still works) then my issues are elsewhere as currently it does
not work and I will need to investigate further.
That being said I believe the ovn-northd should communicate properly
communicate status up the chain otherwise it could cause confusion in
normal operations as that is the place most people are likely to check
first in a Openstack CMS deployment, though that may not be the case for
other CMS deployments. I would not necessarily classify it as a major
issue though as long as it is called out in documentation unless it is
corrected. I will be happy to open a bug on this for tracking once I
figure out my actual issue if that would help.
Cheers,
-C
On 08/28/2017 02:20 AM, Numan Siddique wrote:
On Mon, Aug 28, 2017 at 12:22 PM, Chris Burton
<[email protected] <mailto:[email protected]>> wrote:
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
<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.
I don't think ovn-northd presently sets the status to active for
logical router interfaces (i.e logical switch ports of type router).
Do you think it should set to active ? If its a major issue, I think
it can be addressed.
Thanks
Numan
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] <mailto:[email protected]>
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
<https://mail.openvswitch.org/mailman/listinfo/ovs-discuss>
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
