Description of problem: Run openshift CA certs redeployment playbook against an ha-master ocp-3.7 cluster, it fails at "TASK [restart node]" TASK [Wait for master API to come back online] ****************************************************************************************************************************** ok: [ec2-54-242-50-70.compute-1.amazonaws.com] => {"changed": false, "elapsed": 23, "failed": false, "path": null, "port": 443, "search_regex": null, "state": "started"} TASK [restart node] ********************************************************************************************************************************************************* fatal: [ec2-54-242-50-70.compute-1.amazonaws.com]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to restart service atomic-openshift-node: Job for atomic-openshift-node.service failed because the control process exited with error code. See \"systemctl status atomic-openshift-node.service\" and \"journalctl -xe\" for details.\n"} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-openshift-ca.retry Version-Release number of the following components: openshift-ansible-3.7.0-0.190.0.git.0.129e91a.el7.noarch How reproducible: 100% Steps to Reproduce: 1.Run redeploy-openshift-ca.yml to update the openshift CA cert files ansible-playbook -i host /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/redeploy-openshift-ca.yml -v Actual results: Expected results: Additional info: Ansible inventory file, ansible output of running redeploy-openshift-ca.yml, the logs of atomic-openshift-master-api and atomic-openshift-node on the first master attached.
https://github.com/openshift/openshift-ansible/pull/6031
Verify this bug with openshift-ansible-3.7.0-0.197.0.git.0.f40c09c.el7.noarch.rpm OpenShift CA certs could be updated successfully by playbooks/byo/openshift-cluster/redeploy-openshift-ca.yml. No error during the redeployment.
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/RHSA-2017:3188