Bug 1045221 - neutron:network class does not uplink interface to bridge port on external bridge
Summary: neutron:network class does not uplink interface to bridge port on external br...
Keywords:
Status: CLOSED DUPLICATE of bug 1045137
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-foreman-installer
Version: 4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Crag Wolfe
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks: 1040649
TreeView+ depends on / blocked
 
Reported: 2013-12-19 22:05 UTC by jliberma@redhat.com
Modified: 2014-09-08 05:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-20 00:55:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


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