networking-ovn

neutron-ovn-db-sync-util failing when loading OVNQoSDriver

Bug #1856891 reported by Daniel Alvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
New
Undecided
Taoyunxiang

Bug Description

When running neutron-ovn-db-sync-util on master (Ussuri) I can see this error when the OVNQosDriver gets loaded:

INFO networking_ovn.ml2.qos_driver [None req-3e2a6db0-f488-45e6-8577-2726b4393fbd None None] Starting OVNQosDriver
ERROR neutron.plugins.ml2.managers [None req-3e2a6db0-f488-45e6-8577-2726b4393fbd None None] Mechanism driver 'ovn-sync' failed in update_port_postcommit: KeyError: 'direction'
ERROR neutron.plugins.ml2.managers Traceback (most recent call last):
ERROR neutron.plugins.ml2.managers File "/opt/stack/neutron/neutron/plugins/ml2/managers.py", line 475, in _call_on_drivers
ERROR neutron.plugins.ml2.managers getattr(driver.obj, method_name)(context)
ERROR neutron.plugins.ml2.managers File "/opt/stack/networking-ovn/networking_ovn/cmd/neutron_ovn_db_sync_util.py", line 75, in update_port_postcommit
ERROR neutron.plugins.ml2.managers self.ovn_client.update_port(port, original_port)
ERROR neutron.plugins.ml2.managers File "/opt/stack/networking-ovn/networking_ovn/common/ovn_client.py", line 665, in update_port
ERROR neutron.plugins.ml2.managers if_delete=True)
ERROR neutron.plugins.ml2.managers File "/opt/stack/networking-ovn/networking_ovn/common/ovn_client.py", line 702, in _create_qos_rules
ERROR neutron.plugins.ml2.managers direction = 'from-lport' if qos_options['direction'] ==\
ERROR neutron.plugins.ml2.managers KeyError: 'direction'
ERROR neutron.plugins.ml2.managers
ERROR neutron.plugins.ml2.plugin [None req-3e2a6db0-f488-45e6-8577-2726b4393fbd None None] mechanism_manager.update_port_postcommit failed for port dbbb8d67-0103-4f7b-bb4d-693132a45873: neutron.plugins.ml2.common.exceptions.MechanismDriverError

Revision history for this message
Daniel Alvarez (dalvarezs) wrote :

@Taoyunxiang can you take a look to see if it's related to the latest changes you submitted to the QoS area?

affects: tempest → networking-ovn
Changed in networking-ovn:
assignee: nobody → Taoyunxiang (taoyunxiang)
Revision history for this message
Taoyunxiang (taoyunxiang) wrote :

@Daniel Alvarez
Hi，
It looks lile the failed port has associated a qos polciy,which does not have any rules.
Could you check the vlaue of the qos policy of the failed port? Thanks :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.