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

provider/azurerm: Fixing a bug in the VM Extension Resource #11894

Merged
merged 1 commit into from
Feb 12, 2017

Conversation

tombuildsstuff
Copy link
Contributor

I encountered a scenario where a resource group was deleted via the Portal - but still existed in state. Upon calculating a plan - Terraform throws the following exception:

Error refreshing state: 3 error(s) occurred:

* azurerm_virtual_machine_extension.combined: Error making Read request on Virtual Machine Extension combined: compute.VirtualMachineExtensionsClient#Get: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'XXX' could not be found."

(duplicate output removed)

Updated so that the resource group not existing causes it to be cleared from state (to match other resources) - need to confirm the acceptance tests are still fine (which I'll do a bit later on) - but this fixes the bug I was seeing.

@pmcatominey
Copy link
Contributor

Looks good pending tests 👍

@stack72
Copy link
Contributor

stack72 commented Feb 12, 2017

LGTM! Thank @tombuildsstuff :)

@stack72 stack72 merged commit 705e354 into hashicorp:master Feb 12, 2017
@tombuildsstuff tombuildsstuff deleted the azurerm-vm-extension branch March 28, 2017 15:02
@ghost
Copy link

ghost commented Apr 14, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

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

Successfully merging this pull request may close these issues.

3 participants