Closed hmalinov closed 4 years ago
The tagsClient of VSphereClient seems timeout. If the session is no longer valid and the session needs to be re-saved, Login should be called again before calling SessionID to extract the new session ID. Use the Valid method to check session validity.
if !client.Valid(ctx) {
client.Login(ctx)
}
add to readTagsForResource func
This issue has been open 180 days with no activity. If this issue is reproducible with the latest version of the provider and with Terraform 0.12, please comment. Otherwise this issue will be closed in 30 days.
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
Terraform Version
vSphere Provider Version ./terraform version Terraform v0.11.7
vSphere Provider Version
Affected Resource(s)
Please list the resources as a list, for example:
vsphere_virtual_machine
Terraform Configuration Files
Expected Behavior
Vmware machine is created
Actual Behavior
Terraform fails after 1h 5m with the following error:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
The vmware template was increased from 100GB to 400GB, however the image is created with Packer and it is only 1GB in size.