https://pulumi.com logo
#azure
Title
# azure
h

handsome-state-59775

05/10/2021, 8:51 PM
As part of storage account replacement, the nested file share as well was marked for replacement in preview, however, during the actual update, the following error stops it all:
Copy code
Diagnostics:
  azure-native:storage:FileShare (fileShare):
    error: cannot check existence of resource '/subscriptions/****/resourceGroups/****/providers/Microsoft.Storage/storageAccounts/****/fileServices/default/shares/****': status code 400, {"error":{"code":"FeatureNotSupportedForAccount","message":"File is not supported for the account."}}
Any insights?
1
One of the changes that I'm making is Standard LRS -> Premium LRS
Ref.: https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-create-file-share?tabs=azure-portal#basics
To create a FileStorage storage account, ensure the Performance radio button is set to Premium and Fileshares is selected in the Premium account type drop-down list.
When I change to the following:
Copy code
az.storage.StorageAccount(
    kind=az_storage.Kind.FILE_STORAGE,  # TO MATCH PREMIUM_LRS
    sku=az_storage.SkuArgs(
        name=az_storage.SkuName.PREMIUM_LRS,
    ),
...
)
... I start getting this instead:
Copy code
azure-native:storage:FileShare (fileShare):
    error: autorest/azure: Service returned an error. Status=400 Code="InvalidHeaderValue" Message="The value for one of the HTTP headers is not in the correct format.\nRequestId:3d8b324b-d01a-0068-25ea-453b7f000000\nTime:2021-05-10T22:18:10.0964124Z"
s

sparse-park-68967

05/10/2021, 11:38 PM
Or perhaps this is more relevant: https://github.com/pulumi/pulumi-azure-native/issues/786 - generally suspecting if the api specs for fileshare storage accounts published by Azure have an issue. Could you try and do this through the AZ cli?
h

handsome-state-59775

05/11/2021, 4:46 AM
had to change the access tier to premium as well - thanks for your help!
🎉 1
3 Views