Bug 1694106

Summary:	[crio-tool] Installing or upgrading OCP 3.11 when using crio, keeps changing the crictl.yaml file with the incorrect pathvim
Product:	OpenShift Container Platform	Reporter:	Andre Costa <andcosta>
Component:	Installer	Assignee:	Joseph Callen <jcallen>
Installer sub component:	openshift-ansible	QA Contact:	Weihua Meng <wmeng>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	gpei, jcallen
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openshift-ansible-3.11.104-1.git.0.379a011.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1697679 (view as bug list)		Environment:
Last Closed:	2019-06-06 02:00:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1697679

Description Andre Costa 2019-03-29 14:26:55 UTC

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
openshift-ansible-3.11.92-1.git.0.f2fade7.el7.noarch

rpm -q ansible
ansible-2.6.15-1.el7ae.noarch

ansible --version
ansible 2.6.15
  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)]

How reproducible:
Every time

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

Expected results:
Do not change the crictl.yaml file or set to the correct endpoint.

Additional info:
/usr/share/ansible/openshift-ansible/roles/openshift_node/tasks/upgrade.yml

Comment 1 Joseph Callen 2019-04-03 18:40:08 UTC

https://github.com/openshift/openshift-ansible/pull/11455

Comment 3 Weihua Meng 2019-04-18 06:26:31 UTC

Fixed.

openshift-ansible-3.11.104-1.git.0.379a011.el7

# cat /etc/crictl.yaml 
runtime-endpoint: unix:///var/run/crio/crio.sock

Comment 5 errata-xmlrpc 2019-06-06 02:00:29 UTC

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:0794