Reviewed: https://review.opendev.org/c/openstack/neutron/+/940474 Committed: https://opendev.org/openstack/neutron/commit/a81aa17471a44545f71a044fb0008dc576be2f03 Submitter: "Zuul (22348)" Branch: master
commit a81aa17471a44545f71a044fb0008dc576be2f03 Author: Konstantin Eremin <[email protected]> Date: Thu Jan 30 22:27:11 2025 +0300 OVS: Set log level to INFO for unconfigured ofport cases Log an ERROR if the VIF port has no ofport, which indicates that the port might not be able to transmit traffic. This can happen if the ovs-vswitchd service is down, but the ovsdb-server service is still running. In such cases, the port record might be created in the database, but it won't be processed by ovs-vswitchd, resulting in an empty list ofport value. I was unable to reproduce the ofport=[] scenario using the OpenStack CLI. However, I managed to achieve this by using the «ovs-vsctl add-port» command while the ovs-vswitchd service was stopped. Reusing this port in Neutron is impossible. I believe this situation is highly unlikely to occur in practice, but I decided to leave the check as it is, just in case. When the ofport is set to INVALID_OFPORT, it indicates that the port is in a transitional state and has not yet been fully configured. This is not an error condition but rather a normal part of the port's lifecycle, as it may take some time for the port to be initialized and assigned a valid ofport. Operators should be aware of this state for monitoring purposes, but no immediate action is required. Closes-Bug: #2095576 Change-Id: I0b7e7e8c506a9632aac911c1b4a0d19653dd5239 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2095576 Title: [OVS] False ERROR log message every time when creating VM Status in neutron: Fix Released Bug description: Hi! https://review.opendev.org/c/openstack/neutron/+/850147 "This switch the warning to error as we may be in a situation of no connectivity and this should never happen." I think this switch the warning to error is mistake. This happens every time we create a VM. Every time we see a false error. The logs look like port is configured later and is working, and port is actually working. 2025-01-21 11:34:09,651.651 1 DEBUG neutron.agent.common.async_process [-] Output received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: ...-1... 2025-01-21 11:34:11,343.343 1 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent VIF port: UUID has no ofport configured or is invalid, and might not be able to transmit. (ofport=-1) 2025-01-21 11:34:11,430.430 1 DEBUG neutron.agent.common.async_process [-] Output received from [ovsdb-client monitor Interface name,ofport,external_ids --format=json]: ...5659... Thank you! P.S. Sorry! Nobody answered my question in neutron-ubuntu answers and I created this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2095576/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
