Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2048824

Summary:	[IBMCloud] ibm-vpc-block-csi-node does not specify an update strategy, only resource requests, or priority class
Product:	OpenShift Container Platform	Reporter:	Christopher J Schaefer <cschaefe>
Component:	Storage	Assignee:	Arashad Ahamad <arahamad>
Storage sub component:	Operators	QA Contact:	Chao Yang <chaoyang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	aos-bugs, jnowicki, jsafrane
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2049001 (view as bug list)		Environment:
Last Closed:	2022-08-10 10:45:53 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:	2049001, 2049003

Description Christopher J Schaefer 2022-01-31 22:38:44 UTC

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.

Comment 2 Arashad Ahamad 2022-02-01 12:00:36 UTC

PRs has been raised by cjschaef https://github.com/openshift/ibm-vpc-block-csi-driver-operator/pull/22

Comment 4 Chao Yang 2022-02-08 11:40:35 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 5 Chao Yang 2022-02-08 11:42:00 UTC

Sorry, Update the status in wrong bug.

Comment 6 Chao Yang 2022-02-11 04:16:22 UTC

Passed with 4.11.0-0.nightly-2022-02-10-031822

Comment 8 errata-xmlrpc 2022-08-10 10:45:53 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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:5069