Bug 1739228

Summary:	logging - redeploy certs did not update destinationCACert in kibana route
Product:	OpenShift Container Platform	Reporter:	Rich Megginson <rmeggins>
Component:	Logging	Assignee:	ewolinet
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.11.0	CC:	aos-bugs, ewolinet, jcantril, rmeggins
Target Milestone:	---
Target Release:	3.11.z
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-09-03 15:56:03 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 Rich Megginson 2019-08-08 19:24:48 UTC

Description of problem:

observed TLS errors in the kibana-proxy logs.

http: TLS handshake error from 10.130.6.1:57108: remote error: tls: error decrypting message

Extracted the destinationCACert in the logging-kibana route and compared it to the ca cert in the logging-kibana-proxy secret.  The one from the secret was newer than the one from the route.  After updating the destinationCACert in the logging-kibana route and restarting the kibana pod, the error went away.

Version-Release number of the following components:
3.11
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Russell Teague 2019-08-08 20:22:53 UTC

*** Bug 1739227 has been marked as a duplicate of this bug. ***

Comment 4 Anping Li 2019-08-30 04:34:18 UTC

In 3.11.141, I can see the destinationCACert was updated by  redeploy certs playbooks. and kibana is accessable. So move to verified.

Comment 6 errata-xmlrpc 2019-09-03 15:56:03 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:2580