Bug 2049003 - 4.10: [IBMCloud] ibm-vpc-block-csi-node does not specify an update strategy, only resource requests, or priority class
Summary: 4.10: [IBMCloud] ibm-vpc-block-csi-node does not specify an update strategy, ...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Arashad Ahamad
QA Contact: Chao Yang
: 2049001 (view as bug list)
Depends On: 2048824
Blocks: 2049001
TreeView+ depends on / blocked
Reported: 2022-02-01 10:23 UTC by OpenShift BugZilla Robot
Modified: 2022-03-10 16:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:43:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift ibm-vpc-block-csi-driver-operator pull 23 0 None open [release-4.10] Bug 2049003: IBMCloud: Add critical spec to driver daemonset 2022-02-01 10:23:22 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:43:37 UTC

Description OpenShift BugZilla Robot 2022-02-01 10:23:11 UTC
+++ 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:

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:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

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.

Comment 1 Jan Safranek 2022-02-01 10:29:09 UTC
*** Bug 2049001 has been marked as a duplicate of this bug. ***

Comment 5 Chao Yang 2022-02-08 11:42:52 UTC
  "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

Comment 7 errata-xmlrpc 2022-03-10 16:43:18 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.