Bug 1701427

Summary: [OSP-13] TLS for Manila Internal services
Product: Red Hat OpenStack Reporter: Goutham Pacha Ravi <gouthamr>
Component: puppet-manilaAssignee: Goutham Pacha Ravi <gouthamr>
Status: CLOSED ERRATA QA Contact: Jason Grosso <jgrosso>
Severity: high Docs Contact: Laura Marsh <lmarsh>
Priority: high    
Version: 13.0 (Queens)CC: asimonel, dsedgmen, gcharot, jappleii, jgrosso, jjoyce, jschluet, lmarsh, mgeary, mvelavar, pgrist, pmannidi, slinaber, sputhenp, tbarron, tvignaud, vimartin
Target Milestone: z7Keywords: FeatureBackport, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-manila-12.5.0-6.el7ost Doc Type: Enhancement
Doc Text:
Previously, if you enabled TLS throughout your environment, the communication between internal services, such as the haproxy and the manila API, was not secured. With this update, the manila API supports TLS endpoints on the internal API network.
Story Points: ---
Clone Of: 1701426 Environment:
Last Closed: 2019-07-10 13:05:12 UTC Type: ---
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: 1701425, 1701426    
Bug Blocks:    

Description Goutham Pacha Ravi 2019-04-18 23:30:44 UTC
This bug was initially created as a copy of Bug #1484601 (Stein RFE)
This bug was initially created as a clone of Bug #1701426 (Backport to OSP 14 from OSP 15/Stein)

I am copying this bug because a backport of this feature has been requested to OSP 14 and OSP 13

Description of problem:
TLS Support for Manila internal services: 
 Following flows:
 - client to HAProxy
  - HAProxy to server instance

DFG is requested to test basic flows with TLS enabled and verify encryption by doing a tcpdump.

Comment 1 Goutham Pacha Ravi 2019-04-27 05:41:06 UTC
This change has merged upstream. It is ready to be imported downstream.

Comment 12 errata-xmlrpc 2019-07-10 13:05:12 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/RHBA-2019:1738