Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1340804

Summary:	Including lbaas causing Packstack installation to fail when starting neutron-server
Product:	Red Hat OpenStack	Reporter:	Arie Bregman <abregman>
Component:	openstack-packstack	Assignee:	Ivan Chavero <ichavero>
Status:	CLOSED ERRATA	QA Contact:	Alexander Stafeyev <astafeye>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	abregman, amoralej, amuller, aortega, beagles, ichavero, jjoyce, nlevinki, srevivo, tfreger
Target Milestone:	ga	Keywords:	Automation, AutomationBlocker
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-packstack-8.0.0-4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1349891 (view as bug list)		Environment:
Last Closed:	2016-08-11 12:22:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1349891

Description Arie Bregman 2016-05-30 10:31:09 UTC

Description of problem:

When installing Packstack on multi-node topology, including lbaas, it will fail during the installation when trying to start neutron-server.

The error from the logs is:
"2016-05-27 13:48:32.242 1675 INFO neutron.manager [-] Loading Plugin: lbaas
2016-05-27 13:48:32.431 1675 ERROR neutron.services.service_base [-] No   providers specified for 'LOADBALANCER' service, exiting "

Looks like the issue is that the service provider wasn't configured by the installer, meaning this line should be added to '/etc/neutron/neutron_lbaas.conf':

"service_provider = LOADBALANCER:Haproxy:neutron_lbaas.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default"

Version-Release number of selected component (if applicable): RHOSP 9

How reproducible: 100%

Steps to Reproduce:
1. Include in Packstack answer file the following entry: 'CONFIG_LBAAS_INSTALL: y'
2. Install Packstack on multi-node topology only (no issue with all-in-one)

Actual results:

17:48:28 ERROR : Error appeared during Puppet run: 192.168.1.14_neutron.pp
17:48:28 Error: Could not start Service[neutron-server]: Execution of '/usr/bin/systemctl start neutron-server' returned 1: Job for neutron-server.service failed because the control process exited with error code. See "systemctl status neutron-server.service" and "journalctl -xe" for details.

Expected results: 
Packstack installation completed successfully

Additional info: This only happens for multi-node topologies. When installing on ALL-IN-ONE it works properly.

Comment 2 Alfredo Moralejo 2016-06-24 12:58:53 UTC

This bug has been reported to OSP9, so I guess the right pm-rhel tag is rhos-9.0

Comment 3 Alfredo Moralejo 2016-06-24 13:12:49 UTC

The required patch in packstack requires change https://review.openstack.org/#/c/322411/  to be merged in openstack-puppet-modules for stable/mitaka. Cloned bg to https://bugzilla.redhat.com/show_bug.cgi?id=1349891 to track changes in o-p-m.

Comment 5 Alexander Stafeyev 2016-08-04 13:21:26 UTC

multi node means All-In-One + Compute node? 
Is it good for reproduction ?

Comment 6 Alexander Stafeyev 2016-08-07 11:16:32 UTC

[root@puma09 ~]# rpm -qa | grep pupp
puppet-3.6.2-4.el7sat.noarch
openstack-puppet-modules-8.1.7-2.el7ost.noarch
openstack-packstack-puppet-8.0.0-4.el7ost.noarch

[root@puma09 ~(keystone_admin)]# neutron agent-list 
+--------------------------------------+--------------------+-------------------------------+-------------------+-------+----------------+---------------------------+
| id                                   | agent_type         | host                          | availability_zone | alive | admin_state_up | binary                    |
+--------------------------------------+--------------------+-------------------------------+-------------------+-------+----------------+---------------------------+
| 58736a59-5c5d-4c2f-a43c-b87dc7eedcce | Metadata agent     | puma09.scl.lab.tlv.redhat.com |                   | :-)   | True           | neutron-metadata-agent    |
| 945ab574-df74-4c85-ae55-e03334aeeb58 | L3 agent           | puma09.scl.lab.tlv.redhat.com | nova              | :-)   | True           | neutron-l3-agent          |
| 97c8f2a0-69ea-4a93-8245-338f3b902f65 | Loadbalancer agent | puma09.scl.lab.tlv.redhat.com |                   | :-)   | True           | neutron-lbaas-agent       |


== neutron services ==
neutron-server:                         active
neutron-dhcp-agent:                     active
neutron-l3-agent:                       active
neutron-metadata-agent:                 active
neutron-lbaas-agent:                    active
neutron-openvswitch-agent:              active
neutron-metering-agent:                 active

SETUP: 
node1: Controller+networker
node2: Compute


If this setup is ok I think we can verify this bug. If not, pls provide exact setup details

Comment 7 Alfredo Moralejo 2016-08-08 08:29:52 UTC

To properly verify the fix you need a three nodes setup:

node1: controller
node2: networker
node3: compute

Note that the fixed issue is only seen when using separated controller and networker nodes.

Comment 8 Alexander Stafeyev 2016-08-08 16:20:29 UTC

# Server on which to install OpenStack services specific to the
# controller role (for example, API servers or dashboard).
CONFIG_CONTROLLER_HOST=10.35.160.27

# List the servers on which to install the Compute service.
CONFIG_COMPUTE_HOSTS=10.35.160.39

# List of servers on which to install the network service such as
# Compute networking (nova network) or OpenStack Networking (neutron).
CONFIG_NETWORK_HOSTS=10.35.160.39
 
 
 # Specify 'y' to install OpenStack Networking's Load-Balancing-
# as-a-Service (LBaaS). ['y', 'n']
CONFIG_LBAAS_INSTALL=y


 **** Installation completed successfully ******


[root@puma09 ~]# rpm -qa | grep packstack
openstack-packstack-8.0.0-4.el7ost.noarch
openstack-packstack-puppet-8.0.0-4.el7ost.noarch
[root@puma09 ~]# rpm -qa | grep puppet
puppet-3.6.2-4.el7sat.noarch
openstack-puppet-modules-8.1.7-2.el7ost.noarch
openstack-packstack-puppet-8.0.0-4.el7ost.noarch



[root@puma09 ~(keystone_admin)]# systemctl status neutron
● neutron.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
[root@puma09 ~(keystone_admin)]# systemctl status neutron-server
● neutron-server.service - OpenStack Neutron Server
   Loaded: loaded (/usr/lib/systemd/system/neutron-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2016-08-08 18:32:57 IDT; 45min ago
 Main PID: 30245 (neutron-server)
   CGroup: /system.slice/neutron-server.service

Comment 10 errata-xmlrpc 2016-08-11 12:22:52 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://rhn.redhat.com/errata/RHEA-2016-1597.html