search

Azure / terraform-azurerm-avm-res-cdn-profile

AVM Terraform Module for Azure CDN Profiles
MIT License
1 stars 2 forks source link

Test example "afd_private_link_service_to_LB" in module "avm-res-cdn-profile" fail #37

Open zhangjiale-64 opened 2 weeks ago

zhangjiale-64 commented 2 weeks ago

Describe the issue:

Test the example avm-res-cdn-profile_example_afd_private_link_service_to_LB, there is an error occurs when we open the created resource in azure portal. The subnet/frontend subnet creation fails, because it attempt to enable network policy for the Private Link service on the subnet. The error as follow：

image

Repro Steps:

  1. Clone a terraform template, such as todo-python-mongo-terraform.
  2. Replace the content of the sample afd_private_link_service_to_LB into the main.tf file of terraform, and comment out the content of the output.tf file in terraform.
  3. Login in with command: az login, azd auth login .
  4. Run azd provision.
  5. Open the created resources in azure portal.

Module Version : 0.1.0

Expected behavior: All resources can be created successfully, there is no error in azure portal.

@didayal-msft , @Poven795909 and @jongio for notification.

didayal-msft commented 2 weeks ago

Thanks for submitting the issue @zhangjiale-64 I wanted to confirm if the below setting or any other setting has been changed in the configuration?

image

Please feel free to connect internally

zhangjiale-64 commented 2 weeks ago

Thanks for submitting the issue @zhangjiale-64 I wanted to confirm if the below setting or any other setting has been changed in the configuration?

image

Please feel free to connect internally

The settings in the configuration have not changed.

Poven795909 commented 4 days ago

@zhangjiale-64 I will test at my end and will reach out to you offline for sync on this.

Poven795909 commented 2 days ago

From the screenshot shared, it looks like the error is while applying NSG rules to the subnet. The example code doesnt apply any NSG rules. Looks like the issue due to some organizational policies applied at the subscription level automatically when new subnets are created. The issue is not reproducible at our end with the default configuration.

v-xuto commented 1 day ago

From the screenshot shared, it looks like the error is while applying NSG rules to the subnet. The example code doesnt apply any NSG rules. Looks like the issue due to some organizational policies applied at the subscription level automatically when new subnets are created. The issue is not reproducible at our end with the default configuration.

@jongio Any ideas?