Bug 1349891
| Summary: | Including lbaas causes failure when starting neutron-server | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alfredo Moralejo <amoralej> |
| Component: | openstack-puppet-modules | Assignee: | Jason Guiditta <jguiditt> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 (Mitaka) | CC: | abregman, amoralej, amuller, aortega, beagles, ddomingo, jguiditt, jjoyce, morazi, srevivo, tfreger, tvignaud |
| Target Milestone: | ga | Keywords: | Automation, AutomationBlocker, Triaged |
| Target Release: | 9.0 (Mitaka) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-puppet-modules-8.1.2-1.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
The service providers responsible for configuring VPNaaS and LBaaS created additional files that were never included in the service startup. This prevented neutron-server from starting if LBaaS was enabled.
Previously, the LBaaS service config provider was updated to put service providers directly into /etc/neutron/neutron.conf. Updating VPNaaS to do the same would have caused it to overwrite the 'service_provider' value set by LBaaS, or vice-versa. So to address this, this update moves the 'neutron_config' provider from ini_setting to openstackconfig and adds a variable to neutron::server to manage service providers. This, in turn, prevents VPNaaS and LBaaS from overwriting each others' service_provider values. As a result, enabling LBaaS no longer prevents neutron-server from starting.
|
Story Points: | --- |
| Clone Of: | 1340804 | Environment: | |
| Last Closed: | 2016-08-11 12:27:50 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: | 1340804 | ||
| Bug Blocks: | |||
|
Comment 2
Jason Guiditta
2016-06-24 13:59:47 UTC
multi node means All-In-One + Compute node? Is it good for reproduction ? (In reply to Alexander Stafeyev from comment #4) > multi node means All-In-One + Compute node? > Is it good for reproduction ? I don't use packstack, but my reading of the bug indicates NOT all-in-one is needed to reproduce [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 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. (In reply to Alfredo Moralejo from comment #7) > 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. So if I have a limitation of 2 nodes And I will configure on as controller, and the other one as network node +computenode, this should be good enough right ? Tnx Yes, using: node1: controller node2: compute+network Should be good to check the fix, although is not a typical configuration. # 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-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 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 |