Bug 1045221

Summary: neutron:network class does not uplink interface to bridge port on external bridge
Product: Red Hat OpenStack Reporter: jliberma <jliberma>
Component: openstack-foreman-installerAssignee: Crag Wolfe <cwolfe>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0CC: hateya, jguiditt, jliberma, morazi, rhos-maint, sreichar, yeylon
Target Milestone: ---   
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-20 00:55:56 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: 1040649    

Description jliberma@redhat.com 2013-12-19 22:05:55 UTC
Description of problem: neutron:network class does not uplink interface port to external bridge in OVS. This means L3 agent cannot reach networks via the external bridge. Among other things, floating IP addresses do not work. neutron:compute class does uplink interface port to external bridge.

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

How reproducible: every time

Steps to Reproduce:
1. Deploy foreman server
2. Add host to Neutron controller host group
3. Add host to Neutron networker host group, specifying internal and external bridge parameters
4. Run puppet agent -tv
5. Run ovs-vsctl show to check whether 

Actual results:
Bridge "br-p3p1"
        Port "phy-br-p3p1"
            Interface "phy-br-p3p1"
        Port "br-p3p1"
            Interface "br-p3p1"
                type: internal

Expected results:
Bridge "br-p3p1"
        Port "p3p1"
            Interface "p3p1"
        Port "phy-br-p3p1"
            Interface "phy-br-p3p1"
        Port "br-p3p1"
            Interface "br-p3p1"
                type: internal

Additional info:

Comment 2 Crag Wolfe 2013-12-20 00:55:56 UTC
The root cause for this is the same as BZ 1045137.

*** This bug has been marked as a duplicate of bug 1045137 ***