Hide Forgot
Description of problem: When setting openshift_hosted_logging_deploy=true on a deployment, re-running the config.yaml playbook will fail the deployment as existing objects are found which blocks the deployer from running. As a result, ansible times out and errors out. Version-Release number of selected component (if applicable): 3.4 - pretty sure this applies to prior versions too. Steps to Reproduce: 1. Do default install with openshift_hosted_logging_deploy=true 2. After successful run where logging was attempted, re-run the install with the same configuration parameters. Actual results: Install failure Expected results: Logging configuration wiped out, replaced/reinstalled from scratch.
Can you provide the errors that are seen? Can you also please attach the logs from the Deployer pod?
(In reply to ewolinet from comment #2) > Can you provide the errors that are seen? Can you also please attach the > logs from the Deployer pod? It's the same error you get when you attempt to run the logging deployer after having run the deployer before. It errors out saying templates already exist, or service accounts already exists etc. Depending on where in the process it was. There are options on the deployer template to "redeploy" and avoid these kinds of errors - I don't know if that is the right strategy for the ansible installer though.
Yeah, I'm not sure if using the 'redeploy' mode is the correct approach to avoid those errors... As stated above, with the rewrite for 3.5 we no longer rely on the deployer pod, so we should better handle cases where objects already exist without needing to remove and then reinstall.
Tested logging 3.5.0 deployment with the latest codes from https://github.com/openshift/openshift-ansible -b master, re-run playbooks succeeded, did not encounter error. Logging can be deployed successfully. Set to verified.
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-2017:0903