Bug 1515162

Summary: Octavia.conf is not properly configured
Product: Red Hat OpenStack Reporter: Alexander Stafeyev <astafeye>
Component: puppet-octaviaAssignee: Or Idgar <oidgar>
Status: CLOSED DUPLICATE QA Contact: Alexander Stafeyev <astafeye>
Severity: high Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: astafeye, cgoncalves, jjoyce
Target Milestone: ---Keywords: Triaged
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 13:30:33 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 Alexander Stafeyev 2017-11-20 09:52:47 UTC
Description of problem:
The following should be part of [api_settings] and not [DEFAULT]:


Health manager configs are not set

# bind_ip =
# bind_port = 5555
# controller_ip_port_list example:,
# controller_ip_port_list =

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

How reproducible:

Steps to Reproduce:
Deploy cloud with octavia (ospd)

Comment 1 Nir Magnezi 2017-11-20 10:14:54 UTC
Alex, please specify the RPM versions you tested.

Comment 3 Carlos Goncalves 2017-11-20 12:31:39 UTC
It comes from pupper-octavia and it was fixed in upstream master branch [1] after stable/pike [2]

[1] https://github.com/openstack/puppet-octavia/blob/master/manifests/api.pp#L83
[2] https://github.com/openstack/puppet-octavia/blob/stable/pike/manifests/api.pp#L88

Comment 4 Nir Magnezi 2017-11-20 12:32:04 UTC
Carlos tracked a possible fix that we should backport: https://review.openstack.org/#/c/503985/

Comment 6 Or Idgar 2017-11-30 12:31:49 UTC
Already fixed in openstack gerrit 487450 patch.
Waiting to finish testing this patch then we will merge it.

Comment 7 Nir Magnezi 2017-12-06 13:30:33 UTC
Already covered by bug 1506644
See bug 1506644 comment 6

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