Bug 1287677 - class name of lbaasv2 is not working in neutron.conf
Summary: class name of lbaasv2 is not working in neutron.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 7.0 (Kilo)
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Ihar Hrachyshka
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-02 13:46 UTC by Alexander Stafeyev
Modified: 2016-06-29 13:59 UTC (History)
9 users (show)

Fixed In Version: openstack-neutron-7.0.4-1.el7ost
Doc Type: Bug Fix
Doc Text:
Previously, the lbaasv2 stevedore entry point was not registered in the neutron.service_plugins namespace. This would cause neutron-server to fail if the lbaasv2 alias was used in the service_plugins option instead of the full Python import path to the plug-in. With this update, the missing stevedore alias was added to the package, allowing neutron-server to load the lbaasv2 plug-in using the alias.
Clone Of:
Environment:
Last Closed: 2016-06-29 13:59:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1517125 0 None None None Never
OpenStack gerrit 250822 0 None None None Never
Red Hat Product Errata RHBA-2016:1353 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2016-06-29 17:57:46 UTC

Description Alexander Stafeyev 2015-12-02 13:46:53 UTC 
Description of problem:
In neutron.conf 
# service_plugins =
service_plugins =router,lbaasv2 

this config makes neutron-server to fail, while 

# service_plugins =
service_plugins =router,neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2

work well.

Version-Release number of selected component (if applicable):
openstack-neutron-bigswitch-lldp-2015.1.38-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.2-2.el7ost.noarch
openstack-neutron-metering-agent-2015.1.2-2.el7ost.noarch
openstack-neutron-2015.1.2-2.el7ost.noarch
openstack-neutron-common-2015.1.2-2.el7ost.noarch
openstack-neutron-lbaas-2015.1.2-1.el7ost.noarch
openstack-neutron-ml2-2015.1.2-2.el7ost.noarch
python-neutron-lbaas-2015.1.2-1.el7ost.noarch
python-neutronclient-2.4.0-2.el7ost.noarch
python-neutron-2015.1.2-2.el7ost.noarch


How reproducible:
100%

Steps to Reproduce:
1.enable Lbaasv2 with lbaasv2 class-name in neutron.conf file. 
2.
3.

Actual results:
neutron-server service fails 

Expected results:
neutron-server service should work

Additional info:
logs        http://pastebin.com/CzBRbNxU   

I believe the same issue exists in Liberty ( did not check)
Comment 3 Ihar Hrachyshka 2016-01-07 11:17:16 UTC 
Will be fixed in the next Liberty release: https://review.openstack.org/#/c/250822/
Comment 4 Mike McCune 2016-03-28 22:42:18 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 5 Assaf Muller 2016-06-04 20:00:36 UTC 
(In reply to Ihar Hrachyshka from comment #3)
> Will be fixed in the next Liberty release:
> https://review.openstack.org/#/c/250822/

I imagine there's been an upstream stable/liberty release since January. We should rebase and release an updated OSP 8. Can you please chase this down with Nir?
Comment 6 Ihar Hrachyshka 2016-06-07 12:08:08 UTC 
Assaf, we should solve the issue of rebases not happening in OSP irrespective to the bug.

As for the bug itself, our latest releases for OSP8 include the patch, since we base on 7.0.4.
Comment 8 Toni Freger 2016-06-27 15:48:04 UTC 
neutron conf with below configuration restarted well.
neutron.conf 
# service_plugins =
service_plugins =router,lbaasv2 
(tested on openstack-neutron-7.0.4-7.el7ost.noarch)
Comment 10 errata-xmlrpc 2016-06-29 13:59:10 UTC 
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/RHBA-2016:1353
Note You need to log in before you can comment on or make changes to this bug.