Bug 1710424
Summary: | There is no separate playbook to just perform logging cert rotation | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | ewolinet |
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, mburke, rmeggins |
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Feature: Perform cert rotation for cluster logging without needing to run the install/upgrade playbook and make manual changes on the first master node.
Reason: To prevent the chance of using incorrect inventory settings based on a prior installation of cluster logging just to regenerate certificates, and removing need to perform a required manual step -- done by the playbook instead.
Result: Cluster logging certificates are regenerated, secrets are updated, and components that are required to be restarted to read in the updated certificates are.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-06-26 09:08:11 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
ewolinet
2019-05-15 14:07:49 UTC
The secret prometheus-tls were't refreshed. Could you confirm if this secret should be redeployed? This is only concerned with refreshing the EFK genereated certificates and secrets. Prometheus-tls is managed by the cert signing service https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_logging_elasticsearch/tasks/main.yaml#L362 Added to docs via https://github.com/openshift/openshift-docs/pull/15526 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:1605 |