Bug 1325637

Summary: unable to deploy packstack with vlan tunneling
Product: Red Hat OpenStack Reporter: Eyal Dannon <edannon>
Component: openstack-packstackAssignee: Javier Peña <jpena>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: aortega, jpena, nlevinki, srevivo
Target Milestone: asyncKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-packstack-7.0.0-0.15.dev1702.g490e674.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-29 13:58:14 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
The answer file I used for deployment. none

Description Eyal Dannon 2016-04-10 08:23:13 UTC
Created attachment 1145635 [details]
The answer file I used for deployment.

Description of problem:
I'm trying to deploy packstack, on 2 baremetal's, controller and compute
I'm using the answer file that attached
after the deployment ends, with successful message, the openvswitch on the compute node shows:
[root@compute ~]# ovs-vsctl show
1431f3dd-f564-4eb6-9451-d57bd216abe0
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "2.4.0"


the br-vlan(tunnel) was not created in the compute node.

Version-Release number of selected component (if applicable):
openstack-packstack-7.0.0-0.14
openstack-packstack-puppet-7.0.0-0.14

How reproducible:
Always

Steps to Reproduce:
1.run packstack --answer-file with the answer file I have attached

Actual results:
br-vlan(tunnel) was not created in the openvswitch of the compute node

Expected results:
br-vlan(tunnel) should be created in the compute node.

Additional info:
When using "rhos-release 8 -p 2015-11-24.1" - the openvswitch's configuration is fine.

While using the same answer file on Intel's nodes,the openvswitch's configuration deployed is fine either, so I'm attaching the hardware info:
DELL PowerEdge FC430
Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet

Comment 2 Eyal Dannon 2016-04-11 11:03:35 UTC
I looked into the code, 
in the script /usr/lib/python2.7/site-packages/packstack/plugins/neutron_350.py
under the method :
def create_l2_agent_manifests(config, messages):

the for loop doesn't configures the "$create_bridges" variable for the compute node.

Comment 3 Javier Peña 2016-04-11 11:30:58 UTC
I have proposed https://review.openstack.org/304052 with a fix.

I can think of a corner case where this fix would create an unneeded bridge in the compute nodes, if we are specifying br-ex and br-vlan in a configuration (the scenario proposed in http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html). This should be fixed separately, and I think it would require adding some configuration option to mark which bridges are needed for compute nodes.

Comment 9 errata-xmlrpc 2016-06-29 13:58:14 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:1354