Bug 1747020

Summary: csi-external-provisioner: the "--leader-election-namespace" argument is not supported
Product: OpenShift Container Platform Reporter: Jason Dillaman <jdillama>
Component: StorageAssignee: Fabio Bertinatto <fbertina>
Status: CLOSED ERRATA QA Contact: Chao Yang <chaoyang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, aos-storage-staff, bbennett, calfonso, chaoyang, fbertina, hchiramm, ratamir, tsmetana
Target Milestone: ---   
Target Release: 4.2.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: 2019-10-16 06:38:50 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:

Description Jason Dillaman 2019-08-29 17:08:34 UTC 
Description of problem:
OCS (Rook) uses the external-csi-provisioner container with the "--leadership-election-namespace" argument. This is functional against the k8s 1.3 release but is missing in the OCP 4.2 container.

Version-Release number of selected component (if applicable):
4.2

How reproducible:
100%

Steps to Reproduce:
1. Install OCS
2. Attempt to provision a PVC

Actual results:
The "csi-provisioner" (from csi-external-provisioner image) container fails to start due to the unknown "--leadership-election-namespace" argument.

Expected results:
The container properly starts and supports the argument.

This commit should be pulled into the OCP container image: https://github.com/kubernetes-csi/external-provisioner/commit/e557af7d9a4b600127dceb5d298f5a0c7dea8b64

Here is the deployment yaml from rook: https://github.com/rook/rook/blob/master/cluster/examples/kubernetes/ceph/csi/template/rbd/csi-rbdplugin-provisioner-dep.yaml#L27
Comment 10 errata-xmlrpc 2019-10-16 06:38:50 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, 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-2019:2922