Description of problem: Running /usr/share/ansible/openshift-ansible/playbooks/redeploy-certificates.yml does not redeploy logging certificates although it is expected it redeploys all the certificates (not CAs) of OpenShift components (as it already does with console, catalog, monitoring...). Users must be aware and run /usr/share/ansible/openshift-ansible/playbooks/openshift-logging/redeploy-certificates.yml separately. Version-Release number of the following components: rpm -q openshift-ansible openshift-ansible-3.11.153-2.git.0.ee699b5.el7.noarch rpm -q ansible ansible-2.6.19-1.el7ae.noarch ansible --version ansible 2.6.19 config file = /home/XXXX/ansible.cfg configured module search path = [u'/home/XXXX/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.5 (default, Jun 11 2019, 14:33:56) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)] How reproducible: Always Steps to Reproduce: 1. Run /usr/share/ansible/openshift-ansible/playbooks/redeploy-certificates.yml Actual results: Logging certificates redeployment is not triggered. Expected results: Logging certificates redeployment to be triggered. Additional info:
Moving to Logging team. Any reason why the logging redeploy certificates playbook could not be added to the main redploy playbook?
(In reply to Russell Teague from comment #1) > Moving to Logging team. > Any reason why the logging redeploy certificates playbook could not be added > to the main redploy playbook? I see no reason. @Eric?
I see no reason why not...
Moving back to installer team for impl.
the cert can be deployed with the main redeploy-certificates.yml when use openshift-ansible-3.11.157-1.git.0.10b76ed.el7.noarch
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:4050