-
Notifications
You must be signed in to change notification settings - Fork 455
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
Each apply reboots for attributes update ept_rvi_mode
and hv_mode
#2202
Comments
Hello, aj014506! 🖐 Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle. If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests. |
I'm also running into this issue on vSphere 8, on vSphere 7 the problem does not occur. |
ept_rvi_mode
and hv_mode
Duplicate of #1902 |
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. |
Community Guidelines
Terraform
v1.8.3
Terraform Provider
v2.8.1
VMware vSphere
v8.0.2
Description
Deployed and OVF using below resource. Post deployment, subsequent 'terraform plan' show the attributes
ept_rvi_mode
andhv_mode
are updated and aterraform apply
restarts the virtual machine.Have tried with explicit adding attributes to below resources with either
ept_rvi_mode
=automatic/manual
andhv_mode
=on/off
.Affected Resources or Data Sources
resource_vsphere_virtual_machine
Terraform Configuration
https://github.com/hashicorp/terraform-provider-vsphere/blob/main/website/docs/r/virtual_machine.html.markdown
Debug Output
https://github.com/aj014506/Support_logs/blob/main/Manager_redeployment
Panic Output
No response
Expected Behavior
Post deployment, did not expect to reboot every time.
Actual Behavior
Once VM's deployed did not expected to restart or reboot
Steps to Reproduce
Use below resource to reproduce the issue.
Environment Details
No response
Screenshots
No response
References
No response
The text was updated successfully, but these errors were encountered: