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

Error on changing app service plan #3185

Closed
Leon99 opened this issue Apr 5, 2019 · 7 comments
Closed

Error on changing app service plan #3185

Leon99 opened this issue Apr 5, 2019 · 7 comments

Comments

@Leon99
Copy link

Leon99 commented Apr 5, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform (and AzureRM Provider) Version

Terraform v0.11.13
+ provider.azurerm v1.24.0

Affected Resource(s)

  • azurerm_app_service

Expected Behavior

Resource re-created on changing app service plan as it used to happen before v1.24.0

Actual Behavior

azurerm_app_service.appservice: web.AppsClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=<nil> <nil>

Steps to Reproduce

  1. Change app_service_plan_id
  2. terraform apply

Important Factoids

Not sure if it matters but I'm changing from a Windows plan to a Linux one

@Lucretius
Copy link
Contributor

Lucretius commented Apr 5, 2019

Hi @Leon99 - it looks like in the last release #3048 changed this part of the code to stop forcing a new resource to support migrating between plans. Maybe @tombuildsstuff can shed some light on this particular change? It seems like only "some" apps can be migrated while some need a full create/destroy cycle?

@Leon99
Copy link
Author

Leon99 commented May 1, 2019

@tombuildsstuff I wonder if #3048 could be reverted for now, if fixing it is too hard? We're gradually migrating our services to Linux plans and this bug stops us from upgrading the provider, however, there are fixes in the newer versions that we need.

@tombuildsstuff
Copy link
Contributor

tombuildsstuff commented May 2, 2019

@Leon99 I don't believe reverting #3048 is the right approach here, unfortunately, since that'd break that use-case too. Out of interest does using terraform taint work as a workaround in the interim?

Thanks!

@Leon99
Copy link
Author

Leon99 commented Jun 7, 2019

taint helps, thanks.

@Stolpe
Copy link
Contributor

Stolpe commented Jan 8, 2020

According to https://social.msdn.microsoft.com/Forums/en-US/6d59602e-b67e-4e33-a2b8-fd15b2e111fd/unable-to-quotchange-app-service-planquot-as-no-app-service-plans-are-listed, app service plans can only be changed within the same webspace. Maybe this is something that could be used to determine if an app_service resource can be updated in-place, or if a destroy-and-recreate is needed.

@tombuildsstuff
Copy link
Contributor

Closing this in favour of #6348 which'll highlight the error here

@ghost
Copy link

ghost commented Sep 27, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Sep 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants