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]: net-app-account - Deployment of Volumes in Data Centers Without Zones Fails #4506

Closed
1 task done
jbinko opened this issue Feb 24, 2025 · 2 comments
Closed
1 task done
Assignees
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue

Comments

@jbinko
Copy link
Contributor

jbinko commented Feb 24, 2025

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

I'm not sure

Module Name

avm/res/net-app/net-app-account

(Optional) Module Version

0.7.0

Description

Description: I am encountering an issue with deploying volumes in a data center (DC) that does not support availability zones, specifically in the West US region. The deployment fails with errors related to zones, even though I have tried various configurations.

Steps to Reproduce:

Attempt to deploy volumes in the West US DC.
Do not specify the zones parameter in the volume configuration.
Set the zones parameter to null.
Set the zones parameter to zero.
Expected Result: The volumes should deploy successfully in the West US DC, similar to deployments in other DCs that support zones.

Actual Result: The deployment fails in the West US DC with errors related to zones. The same deployment works fine in other DCs that support zones.

Additional Information:

The issue seems to be specific to the West US DC, which does not support availability zones.
Other DCs with zone support do not exhibit this issue.
Questions:

Is this a bug in the module, or am I missing a specific configuration for DCs without zones?
Are there any known workarounds or additional parameters that need to be set for deployments in DCs without zones?

(Optional) Correlation Id

No response

module nfwus 'br/public:avm/res/net-app/net-app-account:0.7.0' = {
  name: nfwusname
  params: {
    name: nfwusname
    location: wuslocation
    capacityPools: [
      {
        name: 'Pool01'
        serviceLevel: 'Standard'
        size: 4398046511104
        volumes: [
          {
            name: 'fsl'
            creationToken: 'fsl'
            subnetResourceId: wusvnet.outputs.subnetResourceIds[2]
            usageThreshold: 107374182400

            networkFeatures: 'Standard'
            protocolTypes: [
              'CIFS'
            ]
            smbContinuouslyAvailable: true
            /*zones: [
              1
            ]*/
          }
        ]
      }
    ]
    dnsServers: ad_dns_priv_ip
    domainName: domainName
    domainJoinOU: ouPath
    domainJoinUser: domainAdmin
    domainJoinPassword: domainPwd
    smbServerNamePrefix: nfwusname
    aesEncryption: true
  }
}
@jbinko jbinko added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Feb 24, 2025
@jbinko jbinko moved this to Needs: Triage in AVM - Issue Triage Feb 24, 2025
@github-project-automation github-project-automation bot moved this to Needs: Triage in AVM - Module Issues Feb 24, 2025
@avm-team-linter avm-team-linter bot added the Class: Resource Module 📦 This is a resource module label Feb 24, 2025
Copy link

@jbinko, thanks for submitting this issue for the avm/res/net-app/net-app-account module!

Important

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

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.

@github-project-automation github-project-automation bot moved this from Needs: Triage to Done in AVM - Issue Triage Feb 26, 2025
@github-project-automation github-project-automation bot moved this from Needs: Triage to Done in AVM - Module Issues Feb 26, 2025
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 Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue
Projects
Development

No branches or pull requests

2 participants