Description of problem: OCP 3 is using CRI-O container, executing cpma tool didn't generate crio CR Manifest. Version-Release number of selected component (if applicable): OCP3: oc v3.11.153 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-13-160.ec2.internal:8443 openshift v3.11.153 kubernetes v1.11.0+d4cacc0 OCP4: NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-10-11-230724 True False 29h Cluster version is 4.2.0-0.nightly-2019-10-11-230724 CPMA: commit 1a21133cd32b4ca0d4e346fa9a902538759ca051 (HEAD -> release-1.0, origin/release-1.0) How reproducible: always Steps to Reproduce: 1.Setup OCP 3.11 with CRI-O container # oc get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME ip-172-18-1-148.ec2.internal Ready <none> 16h v1.11.0+d4cacc0 172.18.1.148 3.86.2.119 Red Hat Enterprise Linux Server 7.7 (Maipo) 3.10.0-1062.1.2.el7.x86_64 cri-o://1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7-dev ip-172-18-11-134.ec2.internal Ready compute 16h v1.11.0+d4cacc0 172.18.11.134 54.87.40.120 Red Hat Enterprise Linux Server 7.7 (Maipo) 3.10.0-1062.1.2.el7.x86_64 cri-o://1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7-dev ip-172-18-13-158.ec2.internal Ready compute 16h v1.11.0+d4cacc0 172.18.13.158 54.236.15.30 Red Hat Enterprise Linux Server 7.7 (Maipo) 3.10.0-1062.1.2.el7.x86_64 cri-o://1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7-dev ip-172-18-13-160.ec2.internal Ready master 16h v1.11.0+d4cacc0 172.18.13.160 23.20.155.218 Red Hat Enterprise Linux Server 7.7 (Maipo) 3.10.0-1062.1.2.el7.x86_64 cri-o://1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7-dev ip-172-18-14-132.ec2.internal Ready compute 16h v1.11.0+d4cacc0 172.18.14.132 54.166.198.119 Red Hat Enterprise Linux Server 7.7 (Maipo) 3.10.0-1062.1.2.el7.x86_64 cri-o://1.11.16-0.2.dev.rhaos3.11.git3f89eba.el7-dev 2. execute cpma utility Actual results: There is no 100_CPMA-crio-config.yaml generated # tree data data ├── ec2-23-20-155-218.compute-1.amazonaws.com │ └── etc │ ├── containers │ │ └── registries.conf │ ├── crio │ │ └── crio.conf │ ├── etcd │ │ └── etcd.conf │ └── origin │ └── master │ ├── master-config.yaml │ ├── master.server.crt │ └── master.server.key ├── manifests │ ├── 100_CPMA-cluster-config-image.yaml │ ├── 100_CPMA-cluster-config-oauth.yaml │ ├── 100_CPMA-cluster-config-project.yaml │ └── 100_CPMA-cluster-config-sdn.yaml ├── report.html └── report.json Expected results: It should generate 100_CPMA-crio-config.yaml under manifests directory Additional info:
Created attachment 1627224 [details] /etc/crio/crio.conf This is the file from testing environment, it's incomplete, the options pidsLimit, logLevel, logSizeMax are missing from [crio.runtime] section.
As per comment#1 the crio.conf is making CPMA not able to process it. The corresponding CPMA output should actually provide the following message too: WARN[18 Oct 19 12:42 CEST] Skipping Crio: no supported crio configuration found
For validation, please use latest release-1.0/HEAD or on coming build as OCP 4.2 uses crio.conf which relies on tables (crio, crio.runtime, etc), see https://github.com/cri-o/cri-o/blob/master/docs/crio.conf.5.md and https://github.com/fusor/cpma/pull/428 for more details.
Verified, cpma only handles the three options, log_level,log_size_max and pids_limit.
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/RHEA-2020:0440