Red Hat Bugzilla – Bug 1477516
[networking-odl] Full sync broken due to missing plugins
Last modified: 2018-02-05 14:10:03 EST
Description of problem: I noticed the following trace in Neutron's log: 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance [req-76d82cd1-b1ef-46cb-b426-faaaf28b9dae - - - - -] Failed during maintenance operation full_sync.: AttributeError: 'NoneType' object has no attribute 'get_policies' 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance Traceback (most recent call last): 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance File "/usr/lib/python2.7/site-packages/networking_odl/journal/maintenance.py", line 55, in _execute_op 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance operation(session=session) 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", line 86, in full_sync 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance collection_name) 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance File "/usr/lib/python2.7/site-packages/networking_odl/journal/full_sync.py", line 121, in _sync_resources 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance obj_getter = getattr(plugin, 'get_%s' % collection_name) 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance AttributeError: 'NoneType' object has no attribute 'get_policies' 2017-08-02 08:54:55.553 114300 ERROR networking_odl.journal.maintenance Version-Release number of selected component (if applicable): python-networking-odl-11.0.0-0.20170721155128.a047729.el7ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Bug is because an unfortunate change upstream caused full sync to fail if extension plugins aren't loaded. This means full sync will partially run and fail once it reaches a resource it has no plugin for. A fix was proposed upstream
Couple of questions: 1. Do we want QoS loaded with ODL? If so then we need https://review.openstack.org/#/c/492027/ 2. Regardless of #1, this bug's main fix should be in networking-odl. Mike, can you please add the fix to external gerrits on this bz?
(In reply to Tim Rozet from comment #3) > Couple of questions: > 1. Do we want QoS loaded with ODL? If so then we need > https://review.openstack.org/#/c/492027/ > 2. Regardless of #1, this bug's main fix should be in networking-odl. > Mike, can you please add the fix to external gerrits on this bz? We discussed this already, the bug is because only the extention driver is loaded without the service plugin. Networking-ODL is just exhibiting the symptoms of what happens when you have such a mis-configuration, I'm not sure what else you expect it to do.
Even with service plugins including qos, networking-odl throws another error: https://gist.githubusercontent.com/trozet/161259d55c48c51a256e5cbbf68801b5/raw/74656bc02a85af8296e8cfba03833b1f8deda2cf/sync_failure_qos service_plugins = ['odl-router_v2', 'qos', 'trunk'] Attaching full neutron server log. Mike can you look into this?
Created attachment 1313821 [details] neutron server log
(In reply to Tim Rozet from comment #5) > Even with service plugins including qos, networking-odl throws another error: > > https://gist.githubusercontent.com/trozet/161259d55c48c51a256e5cbbf68801b5/ > raw/74656bc02a85af8296e8cfba03833b1f8deda2cf/sync_failure_qos > > service_plugins = ['odl-router_v2', 'qos', 'trunk'] > > Attaching full neutron server log. > > Mike can you look into this? Seems that it's broken and wasn't tested well upstream. I suggest for now we deploy without QoS and target the QoS to RHOS 13
*** Bug 1487782 has been marked as a duplicate of this bug. ***
There full sync runs successfully without errors. Checked with: openstack-tripleo-heat-templates-7.0.3-0.20171023134948.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462