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

[AVM Module Issue]: virtualmachine error when deploying vm with ZRS datadisk #3850

Open
1 task done
gerjon1990 opened this issue Nov 28, 2024 · 8 comments · May be fixed by #3864
Open
1 task done

[AVM Module Issue]: virtualmachine error when deploying vm with ZRS datadisk #3850

gerjon1990 opened this issue Nov 28, 2024 · 8 comments · May be fixed by #3864
Assignees
Labels
Class: Resource Module 📦 This is a resource module Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working

Comments

@gerjon1990
Copy link

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/compute/virtual-machine

(Optional) Module Version

0.10.0

Description

Hi,

Since module version 0.10.0 of virtualmachine we can't deploy a vm with one or more datadisks that will be joined to a availability zone.
The error we get is:

Status Message: A disk with sku 'Premium_ZRS' cannot be created in an availability zone. (Code:OperationNotAllowed)

We did a rollback to version 0.9.0 and deployments run successfull again.

(Optional) Correlation Id

No response

@gerjon1990 gerjon1990 added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Nov 28, 2024

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Type: Bug 🐛 Something isn't working label Nov 28, 2024
@avm-team-linter avm-team-linter bot added the Class: Resource Module 📦 This is a resource module label Nov 28, 2024
@github-project-automation github-project-automation bot moved this to Needs: Triage in AVM - Module Issues Nov 28, 2024
Copy link

@gerjon1990, thanks for submitting this issue for the avm/res/compute/virtual-machine module!

Important

A member of the @Azure/avm-res-compute-virtualmachine-module-owners-bicep or @Azure/avm-res-compute-virtualmachine-module-contributors-bicep team will review it soon!

@gerjon1990
Copy link
Author

gerjon1990 commented Nov 28, 2024

maybe a solution:

When storagetype (sku) is ZRS than set datadisk zone to 0. In the current version the datadisk zone follows the zone of the vm deployment. This is not possible when vm will be joined to a availability zone and the datadisk has sku ZRS.

3891sinneD added a commit to 3891sinneD/bicep-registry-modules that referenced this issue Nov 29, 2024
Possible fix for issue: Azure#3850
@3891sinneD 3891sinneD linked a pull request Nov 29, 2024 that will close this issue
11 tasks

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days label Dec 4, 2024

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

Caution

**This issue requires the AVM Core Team's (@Azure/avm-core-team-technical-bicep) immediate attention as it hasn't been responded to within 6 business days. **

Tip

  • To avoid this rule being (re)triggered, the "Needs: Triage 🔍" and "Status: Response Overdue 🚩" labels must be removed when the issue is first responded to!
  • Remove the "Needs: Immediate Attention ‼️" label once the issue has been responded to.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Immediate Attention ‼️ Immediate attention of module owner / AVM team is needed label Dec 9, 2024
@rahalan rahalan removed Needs: Triage 🔍 Maintainers need to triage still Needs: Immediate Attention ‼️ Immediate attention of module owner / AVM team is needed Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days labels Dec 9, 2024
@rahalan
Copy link
Contributor

rahalan commented Dec 9, 2024

@gerjon1990 thanks! Will look into it

@AlexanderSehr
Copy link
Contributor

Hey @rahalan,
Please triage this issue when you get the chance 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Class: Resource Module 📦 This is a resource module Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working
Projects
Status: Needs: Triage
Development

Successfully merging a pull request may close this issue.

3 participants