Bug 1873175

Summary:	schedule CSI driver operator on master nodes
Product:	OpenShift Container Platform	Reporter:	Hemant Kumar <hekumar>
Component:	Storage	Assignee:	Christian Huffman <chuffman>
Storage sub component:	Operators	QA Contact:	Qin Ping <piqin>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, chuffman, fbertina
Version:	4.6
Target Milestone:	---
Target Release:	4.6.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:	2020-10-27 16:35:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Fabio Bertinatto 2020-08-28 12:34:12 UTC

As part of the verification of this bug, please check if all operators spawn by CSO (AWS EBS, Manila and oVirt) are scheduled in a Control Plane node.

Comment 4 Qin Ping 2020-09-01 03:34:18 UTC

AWS EBS csi operator pods are scheduled to the master, wait for a oVirt cluster to have a check.

Comment 5 Qin Ping 2020-09-02 01:37:11 UTC

oVirt csi driver operator pod runs on master node too.

Verified with: 4.6.0-0.nightly-2020-09-01-070508

Comment 7 errata-xmlrpc 2020-10-27 16:35:19 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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196