Comments (7)
This comment was originally opened by @jen20 as hashicorp/terraform#3870 (comment). It was migrated here as part of the provider split. The original comment is below.
Hi @leonkyneur! I'm not terribly familiar with the underlying API for vSphere to know offhand whether the destroy and create is necessary to add a disk, though it sounds unlikely that this is the case.
The disk order here is interesting though - given the current schema, the ordering is non-deterministic as the disks are a set rather than an array or a list. In the AWS provider the root device (which sounds like the first one in this case) is called out explicitly via a separate block. It may be worth investigating whether that approach is necessary here.
I've tagged this as a bug for now though - thanks for reporting!
from terraform-provider-vsphere.
This comment was originally opened by @chrislovecnm as hashicorp/terraform#3870 (comment). It was migrated here as part of the provider split. The original comment is below.
@jen20 A dev needs to look at it :)
from terraform-provider-vsphere.
This comment was originally opened by @chrislovecnm as hashicorp/terraform#3870 (comment). It was migrated here as part of the provider split. The original comment is below.
@leonkyneur this should be addressed in the dev HEAD branch. If you are able to test, please let me know.
from terraform-provider-vsphere.
Hi,
I'm using Terraform v0.9.11 and I'm experiencing this too.
Is the fix going to get merged into Terraform v0.9.12 maybe?
Thanks!
from terraform-provider-vsphere.
Anybody know if this issue was fixed in 0.10.x version ? I'm having this issue as well
from terraform-provider-vsphere.
Hey @surajsub, I would imagine, more than likely, that this is still an issue. However, with the work going on in #244, this will be solved as this is one of the very specific things that we are targeting in the new VM resource. The ability to place different disks on different datastores has been specifically added and tested, in addition to the ability to use storage vMotion to migrate a single disk only and pin a disk to a specific datastore.
There is documentation on how to do these things in the virtual machine migration section of the new docs - keep in mind the docs are a WIP and not all of the information there is up to date just yet as per some of the more recent developments on #244 - namely the virtual disk diff UX is much better now.
Thanks!
from terraform-provider-vsphere.
This has been fixed with the new version of the resource (additional disks can be added to a clone in pretty much the way you would expect, no special work necessary).
from terraform-provider-vsphere.
Related Issues (20)
- Add instance_uuid parameter to datasource vsphere_virtual_machine HOT 3
- Issue with disks upon restore/snapshot revert HOT 3
- Each apply reboots for attributes update `ept_rvi_mode` and `hv_mode` HOT 4
- Add support to configure auto-start / power-on of virtual machine resources HOT 1
- Add support for [or cluster for 3 zone Deployments HOT 3
- error: error reconfiguring virtual machine: error reconfiguring virtual machine: Invalid operation for device '0' HOT 3
- `customize { windows_options { domain_ou` path containing spaces fails with error HOT 17
- Unable to create/add additional disks to virtual machine HOT 4
- domain_ou unable to find proper ou and dc HOT 5
- error: error reconfiguring virtual machine: error reconfiguring virtual machine: Invalid operation for device '0' HOT 3
- Virtual machine is rebooted when a new SCSI Controller is added to the machine HOT 1
- custom_attributes are not applying to vsphere_vapp_container resource HOT 6
- Add support for adding notes to vsphere_vapp_container HOT 4
- Add support for custom_attributes in resource vsphere_vapp_container HOT 1
- The resource vim.dvs.DistributedVirtualPort is not available in vim.dvs.DistributedVirtualPortgroup HOT 6
- add a disk on a exists vm will recreate this VM HOT 6
- Add support for shutdown or start VM HOT 1
- Creating r/virtual_machine with multiple PCI passthrough devices is not supported
- Plugin did not respond : Stack trace from the terraform-provider-vsphere_v2.8.2_x5.exe plugin HOT 4
- provider is not using HTTPS_PROXY variable HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-vsphere.