-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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 provider - added disk to tf and vm is deleted and created - vm should not have been deleted #7217
Comments
@chrislovecnm Can you post the output of a Also wouldn't hurt to capture all of the logs by setting TF_LOG and running the |
👍 my guess from this is that |
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. |
Expected behavior is a disk is added to the vm. Behavior is vm is deleted and created with two disks.
Testing this against: #7031
But I am thinking this may be happening with other versions. Not certain.
Base TF
Main TF that was applied and worked
The updated main tf -
"vsphere_virtual_machine" "mi-worker-nodes"
has a new disk.The text was updated successfully, but these errors were encountered: