Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694106 - [crio-tool] Installing or upgrading OCP 3.11 when using crio, keeps changing the crictl.yaml file with the incorrect pathvim
Summary: [crio-tool] Installing or upgrading OCP 3.11 when using crio, keeps changing ...
Status: ON_QA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: All
OS: All
Target Milestone: ---
: 3.11.z
Assignee: Joseph Callen
QA Contact: Weihua Meng
Depends On:
Blocks: 1697679
TreeView+ depends on / blocked
Reported: 2019-03-29 14:26 UTC by Andre Costa
Modified: 2019-04-10 19:05 UTC (History)
2 users (show)

Fixed In Version: openshift-ansible-3.11.104-1.git.0.379a011.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1697679 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

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

rpm -q ansible

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:

Note You need to log in before you can comment on or make changes to this bug.