azure-cli icon indicating copy to clipboard operation
azure-cli copied to clipboard

`az storage account blob-service-properties update` fails when privateEndpointConnections exist as of CLI version 2.44.1

Open SavaNDragos opened this issue 2 years ago • 6 comments

az storage account blob-service-properties update fails when privateEndpointConnections exists as of CLI version 2.44.1

Related command az storage account blob-service-properties update --resource-group $ResourceGroupName --account-name $AccountName --enable-restore-policy true --restore-days 30

Describe the bug ERROR: (ConflictFeatureEnabled) Conflicting feature 'privateEndpointConnections' is enabled. Please disable it and retry.

To Reproduce

  • storage account create
  • need a private endpoint on the storage account
  • run the command

Expected behavior The command works and those properties are set (was working in 2.43)

Environment summary azure-cli 2.44.1

SavaNDragos avatar Jan 19 '23 12:01 SavaNDragos

@evelyn-ys for awareness

yonzhan avatar Jan 19 '23 14:01 yonzhan

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

Issue Details

az storage account blob-service-properties update fails when privateEndpointConnections exists as of CLI version 2.44.1

Related command az storage account blob-service-properties update --resource-group $ResourceGroupName --account-name $AccountName --enable-restore-policy true --restore-days 30

Describe the bug ERROR: (ConflictFeatureEnabled) Conflicting feature 'privateEndpointConnections' is enabled. Please disable it and retry.

To Reproduce

  • storage account create
  • need a private endpoint on the storage account
  • run the command

Expected behavior The command works and those properties are set (was working in 2.43)

Environment summary azure-cli 2.44.1

Author: SavaNDragos
Assignees: evelyn-ys
Labels:

Storage, Service Attention, question, customer-reported, Auto-Assign, Azure CLI Team

Milestone: Backlog

ghost avatar Jan 20 '23 00:01 ghost

Can confirm this is an issue. Any of our storage accounts that has any private endpoints cannot have Blob Services settings updated.

ARM template deployments fail, even if those BlobServices settings are the same as existing settings. You can repeat this error in Azure Portal by trying to change the value of the Maximum Restore Point (days ago) in the container point-in-time restore settings

image

The error in the portal is

Failed to update data protection settings for '<storage_account_name>'. Error: Conflicting feature 'privateEndpointConnections' is enabled. Please disable it and retry.

Andrew-George-LG avatar Jan 20 '23 11:01 Andrew-George-LG

getting "Conflicting feature 'privateEndpointConnections' is enabled. Please disable it and retry." .Didn't modified the code Although was not facing this error earlier . Can you help in resolving this.

cypher244 avatar Jan 20 '23 13:01 cypher244

This is not related to Azure CLI. I am using ARM via API calls for some resources and it started to happen today when executing ARM deployment related to storage account.

Vegoo89 avatar Jan 20 '23 15:01 Vegoo89

We had a script in terraform that was doing that call. Don't know how azure CLI actually makes the request. In the latest version of terraform (azurerm plugin) they added the operation to update that property, we tried it and got no failure (think terraform azurerm works with the API, but not 100% certain). Maybe this info helps.

SavaNDragos avatar Jan 20 '23 16:01 SavaNDragos

I have this problem with terraform v1.3.6 and azurerm v3.39.1. Restore policy + private endpoint on a storage account throws the error too. It was working fine before, and then since about 18th Jan 2023, with no code changes, I've started to get the error.

storage.BlobServicesClient#SetServiceProperties: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="ConflictFeatureEnabled" Message="Conflicting feature 'privateEndpointConnections' is enabled. Please disable it and retry."

kpakur avatar Jan 23 '23 08:01 kpakur

Is there any update on this? It blocks all our releases atm.

Edit: Just got update from Microsoft on my ticket. This is known issue and should be resolved by end of 01/25 PST.

Vegoo89 avatar Jan 24 '23 08:01 Vegoo89