Tried the openshift-ansible/playbooks/redeploy-certificates.yml playbook with openshift-ansible-3.9.78-1 If I understand correctly, once we add openshift_node_restart_docker_required=False for openshift-node/private/restart.yml[1] then docker service won't get restart in any cases during redeploy-certificates[2], is this expected? Also, in https://github.com/openshift/openshift-ansible/blob/release-3.9/playbooks/openshift-node/private/restart.yml#L21 openshift_use_crio_only doesn't appear to have a default value, user may doesn't set openshift_use_crio_only var in ansible inventory file. [1]https://github.com/openshift/openshift-ansible/blob/release-3.9/playbooks/redeploy-certificates.yml#L18 [2]https://github.com/openshift/openshift-ansible/blob/release-3.9/playbooks/openshift-node/private/restart.yml#L20
PR: https://github.com/openshift/openshift-ansible/pull/11538
build: openshift-ansible-3.9.80-1
Verify this bug with openshift-ansible-3.9.85-1.git.0.7c950b1.el7.noarch.rpm When running playbooks/redeploy-certificates.yml to renew the certs, docker service will not be restarted. PLAY [Restart nodes] *********************************************************** TASK [Gathering Facts] ********************************************************* ok: [ec2-54-209-35-240.compute-1.amazonaws.com] TASK [Mark node unschedulable] ************************************************* skipping: [ec2-54-209-35-240.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true} TASK [Drain Node for Kubelet restart] ****************************************** skipping: [ec2-54-209-35-240.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true} TASK [Restart docker] ********************************************************** skipping: [ec2-54-209-35-240.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
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:1642