Description of problem:
Current openshift-ansible installer doesn't install podman by default, so debugging issues is complicated.
Version-Release number of the following components:
[cloud-user@crio-bastion ~]$ rpm -q openshift-ansible
[cloud-user@crio-bastion ~]$ rpm -q ansible
[cloud-user@crio-bastion ~]$ ansible --version
config file = /home/cloud-user/ansible.cfg
configured module search path = [u'/home/cloud-user/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /usr/bin/ansible
python version = 2.7.5 (default, Feb 20 2018, 09:19:12) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]
Install OCP using cri-o
Steps to Reproduce:
1. Install ocp using cri-o
2. Try to debug issues
podman not installed by default
podman installed by default
Also cri-tools should be installed.
Antonio was already looking at adding this for 3.10.
Sorry, meant to provide more info before sending this over. It looks like cri-tools shipped in OCP 3.9 and newer channels. And podman is in RHEL 7.5 channels so both packages should be readily available.
we don't have full podman integration with CRI-O right now right? crictl should be enough for debugging afaict. Dan wdyt?
Mrunal, agree this is not a 3.10 blocker?
podman's libpod isn't yet integrated with CRI-O so it isn't ready for debugging CRI-O yet. It can be used to manage images but not the runtime side. It shouldn't be a blocker for 3.10.
Verified according to https://bugzilla.redhat.com/show_bug.cgi?id=1583591#c11
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.