Bug 971770

Summary: Packstack fails to install quantum completely on all nodes when using linuxbridge.
Product: Red Hat OpenStack Reporter: Jaroslav Henner <jhenner>
Component: openstack-packstackAssignee: Terry Wilson <twilson>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: ajeain, aortega, ddomingo, derekh, jkt, mlopes, mmagr, twilson, yeylon
Target Milestone: Upstream M2Keywords: OtherQA
Target Release: 4.0   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-packstack-2013.2.1-0.1.dev691.el6ost Doc Type: Bug Fix
Doc Text:
In previous releases, packstack did not support Linuxbridge. This prevented packstack from correctly installing quantum when specifying the 'linuxbridge' plugin. This release adds Linuxbridge support to packstack, thereby addressing the issue.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 00:05:06 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:
Attachments:
Description Flags
answfile none

Description Jaroslav Henner 2013-06-07 08:57:36 UTC
Created attachment 758062 [details]
answfile

Description of problem:

`--> ssh folsom-rhel6.lithium ls /etc/init.d | grep quantum
# EMPTY HERE
`--> ssh node-01.lithium ls /etc/init.d | grep quantum 
# EMPTY HERE
`--> ssh node-02.lithium ls /etc/init.d | grep quantum 
# EMPTY HERE

Version-Release number of selected component (if applicable):
openstack-packstack-2013.1.1-0.10.dev605.el6ost.noarch

How reproducible:
always

Steps to Reproduce:
1. deploy using attached answfile
2.
3.

Actual results:
no quantum

Expected results:
some quantum

Additional info:

Comment 2 Terry Wilson 2013-06-28 18:13:09 UTC
There are fixes required for both packstack and the upstream puppet-quantum module. I have added an external tracker for the puppet fix. As soon as it is accepted, I can add the packstack fix.

BUT! Even when these fixes go in, the answer-file provided will fail because the VLAN_RANGES=8:64 is in the wrong format. It should be something like "physnet1:8:64". So when testing, make sure to fix that.

Comment 9 errata-xmlrpc 2013-12-20 00:05:06 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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html