Bug 1739226 - logging - redeploy certs created a bogus session-secret
Summary: logging - redeploy certs created a bogus session-secret
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-08 19:17 UTC by Rich Megginson
Modified: 2019-09-03 15:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-03 15:56:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-ansible pull 11817 0 None None None 2019-08-12 16:01:23 UTC
Red Hat Product Errata RHBA-2019:2580 0 None None None 2019-09-03 15:56:11 UTC

Description Rich Megginson 2019-08-08 19:17:47 UTC 
Description of problem:

running the cert redeploy playbook created a bogus session-secret file.  kibana-proxy was complaining that it was too long for AES?

Version-Release number of the following components:

3.11

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 3 Anping Li 2019-08-30 05:13:11 UTC 
No AES error after redeploy certificate. so move to verified.
Comment 5 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
Note You need to log in before you can comment on or make changes to this bug.