Bug 983723 - Multi-node deployment issue due to missing Quantum OVS security groups configuration on controller
Multi-node deployment issue due to missing Quantum OVS security groups config...
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack (Show other bugs)
Unspecified All
unspecified Severity unspecified
: rc
: 4.0
Assigned To: Martin Magr
Ofer Blaut
Depends On:
  Show dependency treegraph
Reported: 2013-07-11 15:36 EDT by Alessandro Pilotti
Modified: 2013-12-19 18:54 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-12-19 18:54:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alessandro Pilotti 2013-07-11 15:36:55 EDT
When using packstack to deploy a multinode setup including:
Compute node: 

nova-compute, quantum-ovs-agent

Network node: 

quantum-ovs-agent, quantum-l3-agent, quantum-dhcp-agent

Controller node:

Nova (except nova-compute and nova-network), Keystone, Glance, Cinder, Horizon and quantum-server

The quantum OVS security groups are configured on the network node, but not on the controller node, resulting in HTTP 500 errors when using the Nova APIs.    

Missing OVS plugin configuration option: firewall_driver 
File: /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini

Version release: 0.20.dev642.el6

How reproducible:
Steps to Reproduce:

1. Deploy RDO with 3 nodes as specified above. 
2. source /root/keystonerc_admin
2. Run "nova list"

Actual results:

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-bee48570-1844-42b1-970d-9ff51e2bb329)

Expected results:

No error.


On the controller node run:

sed -i 's/^#\ firewall_driver/firewall_driver/g' /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
service quantum-server restart
Comment 2 Alvaro Lopez Ortega 2013-11-13 14:09:45 EST
Terry, was this fixed already? Truth be said, we aren't sure.
Comment 3 Terry Wilson 2013-11-13 16:35:31 EST
I'm pretty sure this is fixed. The L2 manifests are executed for api, compute, dhcp, and l3 hosts.
Comment 4 Alvaro Lopez Ortega 2013-12-03 12:27:34 EST
Thanks a million Terry!
Comment 7 Ofer Blaut 2013-12-08 09:35:11 EST
work , tested with 
Comment 10 errata-xmlrpc 2013-12-19 18:54:19 EST
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.


Note You need to log in before you can comment on or make changes to this bug.