Description of problem: When you try to mix Liberty neutron-server and Kilo l2 agent, the following trace back can be seen when security groups are modified on DHCP and IPv6 router ports. ERROR oslo_messaging.rpc.dispatcher [-] Exception during message handling: Endpoint does not support RPC version 1.3. Attempted method: security_groups_provider_updated TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply TRACE oslo_messaging.rpc.dispatcher executor_callback)) TRACE oslo_messaging.rpc.dispatcher File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 195, in _dispatch TRACE oslo_messaging.rpc.dispatcher raise UnsupportedVersion(version, method=method) TRACE oslo_messaging.rpc.dispatcher UnsupportedVersion: Endpoint does not support RPC version 1.3. Attempted method: security_groups_provider_updated This is because neutron-server requires security group API endpoint = 1.3 while Kilo agents are still at 1.2. The fix would be to avoid enforcing the version in OSP8, since OSP7 l2 agents are resistant against changes in argument list of RPC notification endpoints, and are able to handle new OSP8 notifications (just with reduced performance).
verified [heat-admin@overcloud-controller-0 ~]$ sudo vi /usr/lib/python2.7/site-packages/neutron/api/rpc/handlers/securitygroups_rpc.py [heat-admin@overcloud-controller-0 ~]$ rpm -qa |grep openstack-neutron openstack-neutron-7.0.1-8.el7ost.noarch openstack-neutron-common-7.0.1-8.el7ost.noarch openstack-neutron-openvswitch-7.0.1-8.el7ost.noarch openstack-neutron-ml2-7.0.1-8.el7ost.noarch openstack-neutron-metering-agent-7.0.1-8.el7ost.noarch openstack-neutron-lbaas-7.0.0-2.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://rhn.redhat.com/errata/RHEA-2016-0603.html