Terraform PLAN pipeline failing with Error: retrieving VIP info App Service Environment

Question

Terraform PLAN pipeline failing with Error: retrieving VIP info App Service Environment

Suresh Bettadapur 81

Terraform PLAN pipeline failing with Error: retrieving VIP info App Service Environment. Post ASE v2 to v3 migration, terraform script updated in line with ASE v3 syntax.

[ERROR] eval: *terraform.EvalRefresh, err: retrieving VIP info App Service Environment "<ase>" (Resource Group "<RG>"): web.AppServiceEnvironmentsClient#GetVipInfo: Failure responding to request: StatusCode=501 -- Original Error: autorest/azure: Service returned an error. Status=501 Code="NotImplemented" Message="The requested method is not implemented." Details=[{"Message":"The requested method is not implemented."},{"Code":"NotImplemented"},{"ErrorEntity":{"Code":"NotImplemented","ExtendedCode":"51009","Message":"The requested method is not implemented.","MessageTemplate":"The requested method is not implemented.","Parameters":[]}}]

Suresh Bettadapur 81 Reputation points

2024-02-13T10:57:43.48+00:00
Hello @Grmacjon-MSFT Thanks for the response. We already had an existing TF pipeline using which ASE v2 was created sometime back. ASE v2 to v3 migration is done per https://learn.microsoft.com/en-us/azure/app-service/environment/how-to-migrate?pivots=experience-azcli. Migration done successfully following step-by-step documentation. Post migration, made updates in my TF script per v3 syntax. Now, it doesn't give any syntactical errors in TF PLAN, however failing with VIP error

resource "azurerm_app_service_environment_v3" "app_service_environment" { name = var.ase_name subnet_id = data.azurerm_subnet.subnet.id ##pricing_tier = var.pricing_tier ## not applicable for v3 ##front_end_scale_factor = var.front_end_scale_factor # Not applicable to v3 tags = var.tags resource_group_name = var.resource_group_name internal_load_balancing_mode = "Web, Publishing" cluster_setting { name = "DisableTls1.0" value = "1" } }
Fryatt, Darryl (Contractor) 0 Reputation points

2024-02-15T16:02:35.0033333+00:00

@Suresh Bettadapur We are having the same. Did you try running terraform state rm azurerm_app_service_environment.ase as suggested?
Suresh Bettadapur 81 Reputation points

2024-02-15T16:24:39.7566667+00:00

@Fryatt, Darryl (Contractor), not yet. We are having a single state file for all the services and hence was analysing this Is there any risk of executing the state rm azurerm_app_service_environment.ase when we have a single state file for all the services in the RG?
Grmacjon-MSFT 19,151 Reputation points Moderator

2024-02-28T01:03:37.8066667+00:00

@Suresh Bettadapur since the migration was successful, this might be more TF related issue rather than azure app service.Alslo, before using terraform state rm azurerm_app_service_environment.ase carefully consider the dependencies between your resources before executing the rm command.

You could also create a separate state file specifically for the ASE resource if you need to remove it while preserving other resources in the state.
Christopher Capell 5 Reputation points

2024-05-03T20:21:16.4233333+00:00

I had issues with this and had to update our terraform to use azurerm_app_service_environment_v3
Suresh Bettadapur 81 Reputation points

2024-05-06T08:09:15.51+00:00

Yes Fryatt, Darryl (Contractor), I removed the state for the v2 version and imported the state for the v3 version.

Accepted answer

1 additional answer

Your answer

Suresh Bettadapur 81 Reputation points

2024-02-13T10:57:43.48+00:00

Hello @Grmacjon-MSFT Thanks for the response. We already had an existing TF pipeline using which ASE v2 was created sometime back. ASE v2 to v3 migration is done per https://learn.microsoft.com/en-us/azure/app-service/environment/how-to-migrate?pivots=experience-azcli. Migration done successfully following step-by-step documentation. Post migration, made updates in my TF script per v3 syntax. Now, it doesn't give any syntactical errors in TF PLAN, however failing with VIP error

resource "azurerm_app_service_environment_v3" "app_service_environment" { name = var.ase_name subnet_id = data.azurerm_subnet.subnet.id ##pricing_tier = var.pricing_tier ## not applicable for v3 ##front_end_scale_factor = var.front_end_scale_factor # Not applicable to v3 tags = var.tags resource_group_name = var.resource_group_name internal_load_balancing_mode = "Web, Publishing" cluster_setting { name = "DisableTls1.0" value = "1" } }
Fryatt, Darryl (Contractor) 0 Reputation points

2024-02-15T16:02:35.0033333+00:00

@Suresh Bettadapur We are having the same. Did you try running terraform state rm azurerm_app_service_environment.ase as suggested?
Suresh Bettadapur 81 Reputation points

2024-02-15T16:24:39.7566667+00:00

@Fryatt, Darryl (Contractor), not yet. We are having a single state file for all the services and hence was analysing this Is there any risk of executing the state rm azurerm_app_service_environment.ase when we have a single state file for all the services in the RG?
Grmacjon-MSFT 19,151 Reputation points Moderator

2024-02-28T01:03:37.8066667+00:00

@Suresh Bettadapur since the migration was successful, this might be more TF related issue rather than azure app service.Alslo, before using terraform state rm azurerm_app_service_environment.ase carefully consider the dependencies between your resources before executing the rm command.

You could also create a separate state file specifically for the ASE resource if you need to remove it while preserving other resources in the state.
Christopher Capell 5 Reputation points

2024-05-03T20:21:16.4233333+00:00

I had issues with this and had to update our terraform to use azurerm_app_service_environment_v3
Suresh Bettadapur 81 Reputation points

2024-05-06T08:09:15.51+00:00

Yes Fryatt, Darryl (Contractor), I removed the state for the v2 version and imported the state for the v3 version.

Answer 1

Hello @Suresh Bettadapur

I’m sorry to hear that you’re having trouble with your Terraform pipeline. can you please share the full script or the documentation you're following to achieve your scenario?

The error message you’re seeing typically means that the method you’re trying to use isn’t supported by the Azure App Service Environment. This could be due to a number of reasons, such as a change in the API or a misconfiguration in your Terraform script.

Here are a few things you can try to troubleshoot the issue:

Double check that the ASE resource in your Terraform configuration is using the v3 syntax and properties. The API changed between v2 and v3 so the old configuration may no longer be valid.
Try running terraform state rm azurerm_app_service_environment.ase to remove the old ASE state before re-running plan. This forces Terraform to re-read the resource.
Check if any ASE subnet, network security groups, or UDR routes need to be updated in your Terraform config per the v3 networking requirements.
Review the guidance here on migrating Terraform configs: https://docs.microsoft.com/azure/app-service/environment/app-service-environment-infrastructure-migrate#terraform

Best,

Grace

Answer 2

Suresh Bettadapur 81

Hello @Grmacjon-MSFT Want to inform you that the issue is now resolved. I removed the resource from the state. Then, imported the new resource into the state terraform import. Then, the pipeline worked. Thanks

terraform state rm

Grmacjon-MSFT 19,151 Reputation points Moderator

2024-02-28T15:43:28.79+00:00

@Suresh Bettadapur thanks for the update! Glad to hear your issue is resolved

Share via

Terraform PLAN pipeline failing with Error: retrieving VIP info App Service Environment

1 additional answer

Your answer