Bug 1344692 - tripleo set brctlplane IP on external network on compute
Summary: tripleo set brctlplane IP on external network on compute
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 8.0 (Liberty)
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Jiri Stransky
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-10 11:35 UTC by Jaison Raju
Modified: 2019-11-14 08:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-10 15:08:06 UTC
Target Upstream Version:


Attachments (Terms of Use)
templates (3.26 KB, application/x-bzip)
2016-06-10 11:35 UTC, Jaison Raju
no flags Details

Description Jaison Raju 2016-06-10 11:35:18 UTC
Created attachment 1166620 [details]
templates

Description of problem:
When configuring external network on compute , tripleo assigns the brctlplaneIP
on provisioning interface & external interface .
The external interface get configured correctly on controller .
This is the configuration set by os-net-config .
The deployment is complete without errors.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-0.8.14-11.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Duplicate brctlplaneIP on provisioning interface & external interface is assigned .

Expected results:


Additional info:

              -
                type: ovs_bridge
                name: {get_input: bridge_name}
                members:
                  - 
                    type: ovs_bond                                                                       
                    name: bond1                                                                          
                    ovs_options: {get_param: BondInterfaceOvsOptions}                                    
                    members:
                      - 
                        type: interface                                                                  
                        name: em2
                        primary: true                                                                    
                      -                                                                                  
                        type: interface                                                                  
                        name: em3                                                                        
                  -
                    type: vlan
                    device: bond1
                    vlan_id: {get_param: ExternalNetworkVlanID}
                    addresses:
                      -
                        ip_netmask: {get_param: ExternalIpSubnet}
                    routes:
                      -
                        ip_netmask: 10.74.148.0/22
                        next_hop: {get_param: ExternalInterfaceDefaultRoute}
                  - 
                    type: vlan                                                                           
                    device: bond1                                                                        
                    vlan_id: {get_param: StorageNetworkVlanID}
                    addresses:
                      -
                        ip_netmask: {get_param: StorageIpSubnet}

Comment 3 Jaison Raju 2016-06-10 15:08:06 UTC
The network-isolation file needed to use external port yaml for compute ports .
Issue resolved. 

diff network-isolation.yaml network-isolation.yaml.copy
31c31
<   OS::TripleO::Compute::Ports::ExternalPort: ../network/ports/noop.yaml
---
>   OS::TripleO::Compute::Ports::ExternalPort: ../network/ports/external.yaml


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