Bug 1383600

Summary: [ocp-on-osp]Should not allocate additional floating ip for LB when selecting External loadbalancer
Product: OpenShift Container Platform Reporter: Gan Huang <ghuang>
Component: InstallerAssignee: scollier
Status: CLOSED WONTFIX QA Contact: Gan Huang <ghuang>
Severity: low Docs Contact:
Priority: low    
Version: 3.3.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-02 20:08:09 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:

Description Gan Huang 2016-10-11 07:58:25 UTC
Description of problem:
The Heat template would allocate additonal floating ip for LB when selecting External loadbalancer. Actually we don't need the floating ip if we choose external loadbalancer.

Version-Release number of selected component (if applicable):
openshift-on-openstack v0.9.1

How reproducible:
100%

Steps to Reproduce:
1.Create a heat stack which selects external loadbalancer
2.
3.

Actual results:
After stack created successfully, found that a additional floating ip was allocated, and a unused file on bastion host /var/lib/ansible/host_vars/loadbalancer.yml was created:

[root@ghuang7-external-lb-bastion ansible]# cat /var/lib/ansible/host_vars/loadbalancer.yml
ansible_ssh_host: 10.66.147.193
ansible_hostname: ghuang7-external-lb-lb
ansible_default_ipv4:
    address: 10.66.147.193


Expected results:
Unused floating ips and /var/lib/ansible/host_vars/loadbalancer.yml should not be created. 

Additional info:

Comment 1 Jan Provaznik 2016-10-17 07:40:40 UTC
This is needed for supporting multiple loadbalancer types in OSP8. It will be much easier in OSP9 where conditionals can be used in heat template definition. This has lower priority and we can fix it in post GA.

Comment 2 Jan Provaznik 2016-10-19 17:49:50 UTC
I set target release to 3.4.0 to distinguish BZs which will be fixed in a next release.