Open darrens280 opened 1 month ago
Hi @darrens280 , thanks for reporting this!
I can successfully reproduce the issue, this should be upstream API issue that the polling operation API response does not include the properties.provisionState
property, let me report this to the service team.
AzureRMResponseforhttps: //management.azure.com/subscriptions/<redacted>/providers/Microsoft.ElasticSan/locations/westeurope/asyncoperations/<redacted>
{
"properties": {
"creationData": {
"createSource": "None"
},
"sizeGiB": 1,
"storageTarget": {
"targetIqn": "iqn.2024-07.net.windows.core.blob.ElasticSan.es-<redacted>:esanvol2",
"provisioningState": "Succeeded",
"status": "Running",
"targetPortalHostname": "es-<redacted>.z30.blob.storage.azure.net",
"targetPortalPort": 3260
},
"volumeId": "<redacted>"
},
"id": "/subscriptions/<redacted>/resourceGroups/wt-rg-example/providers/Microsoft.ElasticSan/elasticSans/testeswangta/volumeGroups/esanvg/volumes/esanvol2",
"name": "esanvol2",
"type": "Microsoft.ElasticSan/elasticSans/volumeGroups/volumes",
"systemData": {
"createdAt": "2024-07-17T01:45:54.6372003Z",
"createdBy": "<redacted>",
"createdByType": "Application",
"lastModifiedAt": "2024-07-17T01:45:54.6372003Z",
"lastModifiedBy": "<redacted>",
"lastModifiedByType": "Application"
}
}
but I can successfully create if skip the private endpoing, the normal response is like:
{
"properties": {
"managedBy": {
"resourceId": "None"
},
"provisioningState": "Succeeded",
"creationData": {
"createSource": "None"
},
"sizeGiB": 1,
"storageTarget": {
"targetIqn": "iqn.2024-07.net.windows.core.blob.ElasticSan.es-<redacted>:esanvol2",
"provisioningState": "Succeeded",
"status": "Running",
"targetPortalHostname": "es-<redacted>.z28.blob.storage.azure.net",
"targetPortalPort": 3260
},
"volumeId": "<redacted>"
},
"id": "/subscriptions/<redacted>/resourceGroups/wt-rg-example/providers/Microsoft.ElasticSan/elasticSans/testeswangta/volumeGroups/esanvg/volumes/esanvol2",
"name": "esanvol2",
"type": "Microsoft.ElasticSan/elasticSans/volumeGroups/volumes",
"systemData": {
"createdAt": "2024-07-17T01:37:24.3919886Z",
"createdBy": "<redacted>",
"createdByType": "Application",
"lastModifiedAt": "2024-07-17T01:37:24.3919886Z",
"lastModifiedBy": "<redacted>",
"lastModifiedByType": "Application"
}
}
Hi @teowa. Any chance there is some progress with a fix for this? Thank you
Is there an existing issue for this?
Community Note
Terraform Version
1.9.0
AzureRM Provider Version
3.111.0
Affected Resource(s)/Data Source(s)
azurerm_elastic_san_volume
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Elastic SAN Volumes should get created without issue.
Actual Behaviour
Azure Portal confirms the Elastic SAN Volume/s do get created under the Volume Groups, as desired, however the Terraform APPLY shows as failed with the error about
provisioningState
.I did even try add a
time_sleep
resource to wait 60 seconds, before attempting to create theazurerm_elastic_san_volume
however this made no difference.Steps to Reproduce
terraform apply
Important Factoids
n/a
References
No response