Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1692830

Summary: tripleo-heat-templates: TripleO should configure server_certs_key_passphrase for Octavia
Product: Red Hat OpenStack Reporter: Nir Magnezi <nmagnezi>
Component: openstack-tripleo-heat-templatesAssignee: Nir Magnezi <nmagnezi>
Status: CLOSED ERRATA QA Contact: Bruna Bonguardo <bbonguar>
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: cgoncalves, mburns, ramishra
Target Milestone: betaKeywords: Triaged
Target Release: 15.0 (Stein)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-10.5.1-0.20190701110422.889d4d4.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1718905 (view as bug list) Environment:
Last Closed: 2019-09-21 11:20:58 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:
Bug Depends On:    
Bug Blocks: 1718905, 1718940    

Description Nir Magnezi 2019-03-26 14:13:37 UTC 
Description of problem:
=======================
A recent change[1] to Octavia added a parameter named server_certs_key_passphrase, which means that we should generate a password for it to avoid using the default value.

OctaviaServerCertsKeyPassphrase should be added to the list of generated password/secrets.

[1] https://review.openstack.org/#/q/I06d329ca53bc36bd27f7870ae7c7ca0cf18575b2
Comment 2 Nir Magnezi 2019-06-10 11:57:01 UTC 
Merged to upstream master: https://review.opendev.org/#/c/647467/
Proposed backport for stable/stein: https://review.opendev.org/#/c/661954/
Comment 5 Nir Magnezi 2019-06-16 12:21:21 UTC 
stable/stein backport got merged: https://review.opendev.org/#/c/661954/
Comment 8 errata-xmlrpc 2019-09-21 11:20:58 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