Bug 2029416

Summary:	Alibaba Disk CSI driver does not use credentials provided by CCO / ccoctl
Product:	OpenShift Container Platform	Reporter:	Jan Safranek <jsafrane>
Component:	Storage	Assignee:	Jan Safranek <jsafrane>
Storage sub component:	Kubernetes External Components	QA Contact:	Rohit Patil <ropatil>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs, brlu
Version:	4.10
Target Milestone:	---
Target Release:	4.10.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:	2022-03-10 16:32:18 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 Jan Safranek 2021-12-06 13:03:36 UTC

Alibaba Disk CSI driver operator gives the CSI driver env. variable ALIBABA_CLOUD_CREDENTIALS_FILE, pointing to a Secret file provided by CCO / ccoctl with this content:

[default]
type = access_key
access_key_id: xxxxxxx
access_key_secret: yyyyy


The CSI driver ignores this file and loads some credentials from the cloud instance metadata:

time="2021-11-30T19:24:09Z" level=info msg="Get AK: use STS"
time="2021-11-30T19:24:09Z" level=info msg="Starting csi-plugin with sts"

These metadata credentials seem to be enough for the driver to work (provision + attach + mount volumes), still, the CSI driver should use credentials provided by CCO.

This is tracked upstream as https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/issues/557.

Comment 1 Jan Safranek 2021-12-13 16:13:35 UTC

I tested the upstream PR, it works well. It needs to be merged upstream before we can use it.

It will be painful to backport, but that's our job.

Comment 2 Jan Safranek 2022-01-04 09:41:29 UTC

Assigning to Bo Teng, as Jiao Wang (our storage contact in Alibaba) does not have Bugzilla account yet.

The upstream PR https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/pull/572 needs to be reviewed and merged and then we need either Alibaba to do a new release of the driver or Red Hat to backport the patch to 1.1.4, which is quite old.

Comment 3 Jan Safranek 2022-01-04 09:42:14 UTC

Note that this is a blocker and it must be fixed before code freeze!

Comment 5 Brian Lu 2022-01-17 07:06:57 UTC

The upstream PR https://github.com/kubernetes-sigs/alibaba-cloud-csi-driver/pull/572 has been merged.

Comment 11 errata-xmlrpc 2022-03-10 16:32: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.

https://access.redhat.com/errata/RHSA-2022:0056