* Previously, if you deleted the secret, it was not recreated. Even though the certificates were on a disk local to the operator, they weren't rewritten because they hadn't changed. That is, certificates were only written if they changed. The current release fixes this issue. It rewrites the secret if the certificate changes or is not found. Now, if you delete the master-certs, they are replaced.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1901869[*BZ#1901869*])
Description of Problem:
Delete the secret master-cert, the secret couldn't be recreated.
Version-Release number of selected component (if applicable):
CSV: clusterlogging.4.6.0-202011260456.p0
cluster-logging-operator: v4.6.0-202011260456.p0; Last commit ID: 332dec5d433570f7e315b1629159c81abfe936d4"
How Reproducible:
Always
Steps to Reproduce:
1. Deploy cluster-logging
2. oc delete secret master-cert
3. Wait for a while, and check the secret
Actual Result:
master-cert wasn't recreated.
Expected Result:
A new master-cert was generated.
The workaround is to delete the CLO pod as I believe the issue is certs are cached in the pods temp directory. There is logic to not write the certs back if they have not changed. This means if they exist on disk and have not changed or were never written then they never will be written
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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652