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

Running the pipeline a second time gives an error #5

Open
dwschulze opened this issue Nov 23, 2022 · 0 comments
Open

Running the pipeline a second time gives an error #5

dwschulze opened this issue Nov 23, 2022 · 0 comments

Comments

@dwschulze
Copy link

I've implemented the remote backend, and that part seems to be working. The first run of the pipeline creates a VM from an image with no errors. When I run the pipeline a second time (after first deleting the previous VM) I get this error:

2022-11-23T22:13:38.9456834Z �[31m│�[0m �[0m�[1m�[31mError: �[0m�[0m�[1mcompute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status= Code="ConflictingUserInput" Message="Disk boot-osdisk already exists in resource group BOOK.RG. Only CreateOption.Attach is supported." Target="/subscriptions/68fab0aa-ab1e-4e09-a325-46ec73e30541/resourceGroups/book.rg/providers/Microsoft.Compute/disks/boot-osdisk"�[0m

This leads to this issue filed against terraform-provider-azurerm:

The leads to this issue filed against terrafrom-provider-azuremr

It looks like Terraform cannot be executed multiple times from an Azure pipeline to recreate a VM, or to create a separate VM each time it is executed.. I need to be able to create multiple VMs from an image. Is Terraform the right approach for this use case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant