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

vsphere_virtual_machine resource provider getting confused with multiple disks #7372

Closed
ricardclau opened this issue Jun 27, 2016 · 2 comments

Comments

@ricardclau
Copy link
Contributor

Hi

I am having issues when adding disks to vsphere vms, not sure if this is expected but I think I may have hit a bug here, happy to provide more info, etc...

Terraform Version

0.7.0-rc2 (also tested last master Terraform v0.7.0-dev (85ccf3b))

Affected Resource(s)

Please list the resources as a list, for example:

  • vsphere_virtual_machine

Terraform Configuration Files

Adding an extra disk with something like

  disk {
    datastore = "SOME_DATASTORE"
    size = 50
    name = "d_drive"
  }

Debug Output

terraform plan will try to recreate the box but most importantly the state gets confused in existing disks showing this:

disk.2348006000.controller_type:        "scsi" => "scsi" (forces new resource)

No other changes in say the OS drive, just adding an extra disk

Expected Behavior

Not forcing a new resource or at least not show a problem in a disk that has not changed

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform plan after adding the extra disk to the tf file
@ricardclau ricardclau changed the title Vsphere provider getting confused with multiple disks vsphere_virtual_machine resource provider getting confused with multiple disks Jun 27, 2016
@mo-man
Copy link

mo-man commented Apr 26, 2017

I see this bug is still open and reproducible in 0.9.3.

@ghost
Copy link

ghost commented Apr 10, 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 10, 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

4 participants