Bug 1713289

Summary: Octavia amphora certificate files in wrong path and with invalid content
Product: Red Hat OpenStack Reporter: Carlos Goncalves <cgoncalves>
Component: openstack-tripleo-commonAssignee: Carlos Goncalves <cgoncalves>
Status: CLOSED ERRATA QA Contact: Bruna Bonguardo <bbonguar>
Severity: high Docs Contact:
Priority: urgent    
Version: 15.0 (Stein)CC: mburns, slinaber
Target Milestone: betaKeywords: AutomationBlocker, Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-10.7.1-0.20190625154433.5751fc7.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-21 11:22:28 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:

Description Carlos Goncalves 2019-05-23 10:43:30 UTC
Description of problem:

Octavia amphora certificate files are being created in an unexpected path and with invalid content
[root@controller-2 log]# ls /var/lib/config-data/puppet-generated/ | grep octavia
octavia
octaviaca_cert_path
octaviaca_private_key_path
octaviaclient_cert_path
octavia.md5sum


[root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaca_cert_path
ca_cert_content[root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaca_private_key_path
private_key_content[root@controller-2 log]# cat /var/lib/config-data/puppet-generated/octaviaclient_cert_path
service_pem_content[root@controller-2 log]#

Version-Release number of selected component (if applicable):
RHOS_TRUNK-15.0-RHEL-8-20190520.n.2

How reproducible:
100%

Steps to Reproduce:
1. Deploy OSP 15 with Octavia enabled
2. Create amphora load balancer

Actual results:
Load balancer will not be created successfully. It will go into ERROR provisioning_status

Expected results:
Amphora load balancer would be successfully provisioned and go ACTIVE.

Comment 9 errata-xmlrpc 2019-09-21 11:22:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811