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

Data Disk Attachment: obtaining a basic view of the VM rather than the Instance View #1855

Merged
merged 1 commit into from Aug 31, 2018

Conversation

tombuildsstuff
Copy link
Member

@tombuildsstuff tombuildsstuff commented Aug 31, 2018

This matches the usages across the Provider which I believe should should fix #1600 - but I've been unable to reliably reproduce that issue. Additional context is in this comment: #1600 (comment)

@tombuildsstuff
Copy link
Member Author

Tests pass for this branch:

Copy link
Member

@bflad bflad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@tombuildsstuff tombuildsstuff merged commit 7e87a0e into master Aug 31, 2018
@tombuildsstuff tombuildsstuff deleted the vm-data-disk-attachment branch August 31, 2018 13:03
tombuildsstuff added a commit that referenced this pull request Aug 31, 2018
torresdal pushed a commit to torresdal/terraform-provider-azurerm that referenced this pull request Aug 31, 2018
torresdal pushed a commit to torresdal/terraform-provider-azurerm that referenced this pull request Aug 31, 2018
@whytoe
Copy link
Contributor

whytoe commented Sep 7, 2018

@tombuildsstuff I am still having issues with this

  • provider.azurerm: version = "~> 1.14"

  • azurerm_virtual_machine_data_disk_attachment.attach: Error updating Virtual Machine "myVM" (Resource Group "myRGP") with Disk "myVM-disk1": compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidRequestContent" Message="The request content was invalid and could not be deserialized: 'Could not find member 'resources' on object of type 'ResourceDefinition'. Path 'resources', line 1, position 2049.'."

@tombuildsstuff
Copy link
Member Author

@whytoe sorry to hear this is still an issue for you - I've spent a while trying to repro this and have been unsuccessful, unfortunately - so this was a best effort fix without being able to verify one way or the other.

Out of interest is this happening repeatedly for you? If so - would you be able to capture the http traffic (using either TF_LOG=1 or a Proxy of some kind [e.g. Charles Proxy/Fiddler and http_proxy=http://localhost:8888 https_proxy=http://localhost:8888 terraform plan]) so that we could investigate this further?

Thanks!

@whytoe
Copy link
Contributor

whytoe commented Sep 7, 2018

@tombuildsstuff ya I saw the other thread and didn't want to take over someone else issue
Give me 20 minutes

@tombuildsstuff
Copy link
Member Author

@whytoe awesome, thanks a lot :)

@whytoe
Copy link
Contributor

whytoe commented Sep 7, 2018

@tombuildsstuff I forgot to tag you in this post, oops

https://gist.github.com/whytoe/64ea636330940c41d6edab976d9317d0
I changed VM, Subscription and any unique identifiers to myResource format

It looks like the api is not accepting the json post

Here is the Microsoft Rest API documentation for the API 2017-12-01

https://docs.microsoft.com/en-us/rest/api/compute/virtualmachines/createorupdate#create_a_vm_with_empty_data_disks.

@ghost
Copy link

ghost commented Mar 6, 2019

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!

@hashicorp hashicorp locked and limited conversation to collaborators Mar 6, 2019
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.

azurerm_virtual_machine_data_disk_attachment attach fails for more than 1 disks.
3 participants