Stoyan Zhelyazkov

Hey @mristok did you run the acceptance tests in "vsphere/resource_vsphere_virtual_machine_test.go"? Your change seems safe-enough but it won't hurt to make sure everything is okay. It would be even better if...

I tested the change with some mock GPUs on my environment, seems to work fine

Duplicate of #2116

@tenthirtyam We can't make them computed and keep the default value at the same time. Terraform does not permit this combination. Just removing the defaults solves the problem. We can...

Going to reintroduce the [fix](https://github.com/hashicorp/terraform-provider-vsphere/pull/2172) as a breaking change in the next major release

> Vsphere provider 2.8.1 Vsphere 8.0.2.00300 > > I'm still having the issue, VM are rebooting. I've implemented the workaround with the lifecycle from above. > > Just to make...

Hey @erSitzt the only way I was able to reproduce this was to change the failover order outside TF and attempt to plan/apply the original configuration again. There is no...

> @spacegospod Still happening with current version `v2.8.2` > > It still happens for all hosts after some time.. not sure what is triggering it. BUT i can provoke this...

Looks like entering maintenance mode was the missing piece of the puzzle. I was able to reproduce the bug in 2 out of 6 attempts, it doesn't happen every time...