Bug 2099968

Summary:	[Azure-File-CSI] failed to provisioning volume in ARO cluster
Product:	OpenShift Container Platform	Reporter:	Wei Duan <wduan>
Component:	Storage	Assignee:	Fabio Bertinatto <fbertina>
Storage sub component:	Kubernetes External Components	QA Contact:	Wei Duan <wduan>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	fbertina
Version:	4.11
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:		Environment:
Last Closed:	2022-08-10 11:18:57 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 Wei Duan 2022-06-22 06:06:48 UTC

Description of problem:
In 4.11 ARO cluster, creating pvc with Azure-File CSI Driver(storageclass azurefile-csi), PVC is in Pending status with following message: (Not sure if it is the same issue with https://bugzilla.redhat.com/show_bug.cgi?id=2095049)

  Warning  ProvisioningFailed    5m53s (x15 over 32m)   file.csi.azure.com_wduan-0622c-aro-fz4wf-master-0_784ba8fa-3d0e-43ae-9ace-9d1efdca85e9  failed to provision volume with StorageClass "azurefile-csi": rpc error: code = Internal desc = failed to ensure storage account: could not list storage accounts for account type Standard_LRS: Retriable: false, RetryAfter: 0s, HTTPStatusCode: 404, RawError: azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.Storage/storageAccounts?api-version=2021-02-01: StatusCode=404 -- Original Error: adal: Refresh request failed. Status Code = '404'. Response body:  Endpoint https://login.microsoftonline.com/oauth2/token

$ oc get pvc mydep-pvc-02
NAME           STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    AGE
mydep-pvc-02   Pending                                      azurefile-csi   31m


Version-Release number of selected component (if applicable):
ARO cluster
$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-2022-06-21-151125   True        False         139m    Cluster version is 4.11.0-0.nightly-2022-06-21-151125

How reproducible:
Always

Steps to Reproduce:
See Description.

Actual results:
PVC stay in pending status.

Expected results:
PVC should be provioned successfully.

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

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

Additional info:

Comment 3 Wei Duan 2022-06-23 12:51:26 UTC

Verified passed on 4.11.0-0.nightly-2022-06-23-044003.

$ oc get pod,pvc
NAME                               READY   STATUS    RESTARTS   AGE
pod/mydeploy-04-645698f5dd-cnt7r   1/1     Running   0          64s

NAME                                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS    AGE
persistentvolumeclaim/mydep-pvc-04   Bound    pvc-eab14684-4193-4817-8952-ad5b497a1bb5   1Gi        RWO            azurefile-csi   64s

Comment 5 errata-xmlrpc 2022-08-10 11:18:57 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