3.10 has the same issue.
+++ This bug was initially created as a clone of Bug #1694106 +++
Description of problem:
The file /etc/crictl.yaml keeps being updated with the incorrect runtime-endpoint and it needs to be change after running installation or upgrade playbooks, otherwise we get always a warning message when using crictl tool saying the runtime-endpoint is incorrect.
"Using "/var/run/crio/crio.sock" as endpoint is deprecated, please consider using full url format "unix:///var/run/crio/crio.sock""
Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /bin/ansible
python version = 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]
Steps to Reproduce:
1. Run installation or upgrade playbook
2. Check some object using crictl tool: crictl ps
3. Correct the file and check tool again:
# echo 'runtime-endpoint: unix:///var/run/crio/crio.sock' > /etc/crictl.yaml
# crictl ps
Do not change the crictl.yaml file or set to the correct endpoint.
--- Additional comment from Joseph Callen on 2019-04-03 18:40:08 UTC ---
In build: openshift-ansible-3.10.137-1
# cat /etc/crictl.yaml
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.