Bug 1344692

Summary: tripleo set brctlplane IP on external network on compute
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: openstack-tripleo-heat-templatesAssignee: Jiri Stransky <jstransk>
Status: CLOSED NOTABUG QA Contact: Arik Chernetsky <achernet>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: jraju, mburns, rhel-osp-director-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-10 15:08: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
templates none

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