Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug Report]: Re-deployment of Storage Accounts fails after upgrade to 0.11.0 #3949

Closed
krbar opened this issue Sep 11, 2023 · 0 comments · Fixed by #3983
Closed

[Bug Report]: Re-deployment of Storage Accounts fails after upgrade to 0.11.0 #3949

krbar opened this issue Sep 11, 2023 · 0 comments · Fixed by #3983
Assignees
Labels
bug Something isn't working

Comments

@krbar
Copy link
Contributor

krbar commented Sep 11, 2023

Describe the bug

Storage accounts, which were deployed with the 0.10.0 version of the Storage Account module, cannot be re-deployed with the release 0.11.0 of the Storage Account module.
The deployment fails with the error Status Message: The property 'isNfsV3Enabled' was specified in the input, but it cannot be updated as it is read-only.
This is because of change implemented in #3290 in response to #3106. While I think this change is necessary, it causes issues for older storage accounts. The "older" storage accounts, deployed with CARML 0.10.0 have isNfsV3Enabled=false set, the new module version 0.11.0 is only able to set isNfsV3Enabled=true or isNfsV3Enabled=null, but it cannot set isNfsV3Enabled=false.

To reproduce

  • Deploy a storage account using CARML release 0.10.0
  • "Upgrade" CARML to 0.11.0
  • Address breaking changes/renamed parameters (i.e. skuName)
  • Re-deploy the storage account

Code snippet

No response

Relevant log output

No response

@krbar krbar added the bug Something isn't working label Sep 11, 2023
@AlexanderSehr AlexanderSehr linked a pull request Sep 16, 2023 that will close this issue
4 tasks
@AlexanderSehr AlexanderSehr self-assigned this Sep 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Closed
Development

Successfully merging a pull request may close this issue.

2 participants