Description of problem:
Using openshift_crio_use_rpm=True tries to install cri-o as system container, since system container install is not preferred anymore can we make openshift_crio_use_rpm=True by default.
Version-Release number of the following components:
Steps to Reproduce:
1. use openshift_crio_use_rpm=True
Install tries to install cri-o as system container.
cri-o should be installed as rpm by default.
I believe this should belong to the installer team?
By my reading/understanding, ``openshift_crio_use_rpm`` can simply be ignored, since cri-o will always/only be installed as an RPM. That simplifies the situation to just ``openshift_use_crio``. Working on a PR to take care of this in the installer (and testing it)...
...actually, it looks like this was already fixed by https://github.com/openshift/openshift-ansible/pull/8427
...sure enough, all you need is `openshift_use_crio=true``.
I also confirmed this is upstream under tag ``openshift-ansible-3.10.0-0.50.0`` and master as (4796c1d0). We'll also give this a final check prior to actual release.
and env setup successfully.
# oc version
features: Basic-Auth GSSAPI Kerberos SPNEGO
# oc get nodes -o wide
NAME STATUS ROLES AGE VERSION EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-172-18-1-68.ec2.internal Ready master 3m v1.10.0+b81c8f8 126.96.36.199 Red Hat Enterprise Linux Server 7.5 (Maipo) 3.10.0-862.2.3.el7.x86_64 cri-o://1.10.2-dev
ip-172-18-11-51.ec2.internal Ready compute 2m v1.10.0+b81c8f8 188.8.131.52 Red Hat Enterprise Linux Server 7.5 (Maipo) 3.10.0-862.2.3.el7.x86_64 cri-o://1.10.2-dev
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.