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

Bug 1641052

Summary:	Updating SSL/TLS Certificates procedure needs to include haproxy restart
Product:	Red Hat OpenStack	Reporter:	nalmond
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	12.0 (Pike)	CC:	bperkins, michele
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:	2019-05-22 09:51:52 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 nalmond 2018-10-19 13:47:44 UTC

Description of problem:
When following the procedure in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html/advanced_overcloud_customization/sect-enabling_ssltls_on_the_overcloud#updating_ssl_tls_certificates to update the overcloud ssl certs, the new certificate is pushed through but haproxy is still using the old cert.

Restarting the haproxy containers seems to resolve this.

$ sudo pcs resource restart haproxy-bundle

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


How reproducible:
Seen in at least 2 environments

Steps to Reproduce:
1. Deploy overcloud with ssl
2. Attempt to update ssl certificate by re-deploying with the updated template
3.

Actual results:
Haproxy is still using the old cert

Expected results:
Haproxy uses the new cert

Additional info:
Have not verified but this likely applies to RHOSP 13 as well