+++ This bug was initially created as a clone of Bug #2048824 +++ Description of problem: Version-Release number of selected component (if applicable): IPI 4.10 on IBM Cloud How reproducible: 100% Steps to Reproduce: 1. Deploy IPI cluster on IBM Cloud 2. Run OCP Conformance tests (openshift/conformance/parallel) Actual results: OCP test results fail as a result of incomplete spec for the ibm-vpc-block-csi-node daemonset [sig-arch] Managed cluster should ensure platform components have system-* priority class associated [Suite:openshift/conformance/parallel] [sig-arch] Managed cluster should only include cluster daemonsets that have maxUnavailable update of 10 or 33 percent [Suite:openshift/conformance/parallel] [sig-arch] Managed cluster should set requests but not limits [Suite:openshift/conformance/parallel] Expected results: Managed cluster daemonsets should have a maxUnavailable and update strategy set, a priority class set, and only set resource requests (not limits), including ibm-vpc-block-csi-node. Master Log: n/a Node Log (of failed PODs): n/a PV Dump: n/a PVC Dump: n/a StorageClass Dump (if StorageClass used by PV/PVC): n/a Additional info: IBM Cloud is working on a fix for this issue, in an attempt to address failing OCP Conformance tests for the 4.10 GA with IBM Cloud support of IPI.
*** Bug 2049001 has been marked as a duplicate of this bug. ***
{ "rollingUpdate": { "maxSurge": 0, "maxUnavailable": "10%" }, "type": "RollingUpdate" } oc get daemonset.apps/ibm-vpc-block-csi-node -o json | grep -i priorityClassName "priorityClassName": "system-node-critical", Passed with 4.10.0-0.nightly-2022-02-07-162517
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