terraform-provider-azurerm: Error while creating storage account
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave “+1” or “me too” comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Terraform (and AzureRM Provider) Version
Terraform v0.12.3
- provider.azurerm v1.32.0
- provider.null v2.1.2
- provider.random v2.1.2
- provider.template v2.1.2
Affected Resource(s)
azurerm_storage_account
Terraform Configuration Files
` variable “storage_name” {} variable “region” {} variable “resource_group_name” {} variable “environment” {} variable “usage” {} variable “dependencies” { type = list(string) }
resource “null_resource” “dependency_getter” { triggers = { my_dependencies = join(“,”, var.dependencies) } }
Generate random text for a unique name
resource “random_id” “randomId” { keepers = { # Generate a new ID only when a new resource group is defined resource_group = var.resource_group_name } byte_length = 8 }
resource “azurerm_storage_account” “stgacc” { name = “diag${random_id.randomId.hex}” resource_group_name = var.resource_group_name location = var.region account_tier = “Standard” account_replication_type = “LRS”
tags = { environment = var.environment }
depends_on = [null_resource.dependency_getter] }
resource “azurerm_storage_account” “stgaccount” { name = var.storage_name resource_group_name = var.resource_group_name location = var.region account_tier = “Standard” account_replication_type = “LRS”
tags = { environment = var.environment }
depends_on = [null_resource.dependency_getter] } `
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key: https://keybase.io/hashicorp
Debug Output
Panic Output
Expected Behavior
Terraform successful creation statement.
Actual Behavior
Error: Error reading queue properties for AzureRM Storage Account “diag5d01f638b17d3d58”: queues.Client#SetServiceProperties: Failure responding to request: StatusCode=403 – Original Error: autorest/azure: error response cannot be parsed: “\ufeff<?xml version=\"1.0\" encoding=\"utf-8\"?><Error>AuthorizationPermissionMismatch
<Message>This request is not authorized to perform this operation using this permission.\nRequestId:4554aa06-9003-00dc-7bb2-43c9be000000\nTime:2019-07-26T13:01:08.2516744Z</Message></Error>” error: invalid character ‘ï’ looking for beginning of value
Error: Error reading queue properties for AzureRM Storage Account “tboxfkartstorage”: queues.Client#SetServiceProperties: Failure responding to request: StatusCode=403 – Original Error: autorest/azure: error response cannot be parsed: “\ufeff<?xml version=\"1.0\" encoding=\"utf-8\"?><Error>AuthorizationPermissionMismatch
<Message>This request is not authorized to perform this operation using this permission.\nRequestId:df5abaf5-5003-0010-03b2-43d411000000\nTime:2019-07-26T13:00:58.3772146Z</Message></Error>” error: invalid character ‘ï’ looking for beginning of value
Steps to Reproduce
terraform apply
Important Factoids
The resources are created and visible in the azure portal with proper configuration. But the script ends without success message.
References
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 25
- Comments: 47 (21 by maintainers)
Still doing it in eastus with 1.3x, working with 1.28.
I thought this was related to my account coming off the free trial, but I ran
az login
again and theaz account
information corresponds to the current portal state. This configuration reproduces the bug:@tombuildsstuff I’m not sure it’s related, my error is more like above
This has been released in version 1.33.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:
I got these errors with Azure CLI authenticating as myself - the subscription owner, so I definitely have all the required permissions
Hey guys, I ended up rolling back the azure rm provider to 1.28 and looks like this is fixed on my end so it’s definitely something in the 1.3x release.