Bug 2028731
| Summary: | The containerruntimeconfig controller has wrong assumption regarding the number of containerruntimeconfigs | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qi Wang <qiwan> |
| Component: | Node | Assignee: | Qi Wang <qiwan> |
| Node sub component: | Kubelet | QA Contact: | Weinan Liu <weinliu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | aos-bugs, weinliu |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-10 16:31:36 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: | 2032985 | ||
weinliu Could you test it using the different label for master and worker pool instead of reapplying the same label? $ oc get ContainerRuntimeConfig NAME AGE custom-pidslimit 6m30s custom-pidslimit-master 7s <== Verified to get fixed custom-pidslimit10 4m22s custom-pidslimit11 4m14s custom-pidslimit2 5m59s custom-pidslimit3 5m52s custom-pidslimit4 5m45s custom-pidslimit5 5m39s custom-pidslimit6 5m32s custom-pidslimit7 5m25s custom-pidslimit8 5m20s custom-pidslimit9 5m10s $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2021-12-14-083101 True False 4h55m Cluster version is 4.10.0-0.nightly-2021-12-14-083101 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056 |
Description of problem: $ oc get mc NAME GENERATEDBYCONTROLLER IGNITIONVERSION AGE 00-master c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 00-worker c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 01-master-container-runtime c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 01-master-kubelet c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 01-worker-container-runtime c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 01-worker-kubelet c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 99-master-generated-containerruntime c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 14m 99-master-generated-containerruntime-2 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 7m43s 99-master-generated-containerruntime-3 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 7m17s 99-master-generated-containerruntime-7 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 43s 99-master-generated-containerruntime-8 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 30s 99-master-generated-containerruntime-9 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 20s 99-master-generated-registries c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 99-master-ssh 3.2.0 64m 99-worker-generated-containerruntime c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 16m 99-worker-generated-containerruntime-1 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 11m 99-worker-generated-containerruntime-4 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 102s 99-worker-generated-containerruntime-5 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 82s 99-worker-generated-containerruntime-6 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 70s 99-worker-generated-registries c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m 99-worker-ssh 3.2.0 64m rendered-master-15196ba60f515b1fdce819754727ff7d c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 14m rendered-master-83650f30ed153394209ca0b54339dd8c c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 7m40s rendered-master-cf39fe972d6d33c8d232e5c3d3a6b0b9 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m rendered-worker-50b2c5c16d00a57a13e27948c2ea9fa4 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 60m rendered-worker-b57e01b5ebc33a82ddf4e5d729a19835 c533e61a9e4f459b882f94214713efff8b1e8604 3.2.0 16m $ oc create -f /home/qiwan/test-crds/overlay-size.yml containerruntimeconfig.machineconfiguration.openshift.io/producebug created $ oc describe containerruntimeconfig.machineconfiguration.openshift.io/producebug Status: Conditions: Last Transition Time: 2021-12-03T04:09:25Z Message: could not get ctrcfg key: max number of supported ctrcfgs (10) has been reached. Please delete old ctrcfgs before retrying Status: False Type: Failure Observed Generation: 1 Events: <none> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create some containerruntimeconfigs to master pool after creating containerruntimeconfigs to worker pool. Actual results: Report status: Master pool containerruntimeconfigs reached the upper limit 10, but the actual number of containeruntimeconfigs is less than 10. The generated machine config names with the suffix are mismatched between worker pool and master pool mc Expected results: The limit of 10 is for each pool. Additional info: