Closed Xav-Pe closed 9 months ago
elsudano
commented
3 years ago Hi xav-pe
Sorry for the delay in my answer, I think that I fixed the issue in the version 0.2.2 the provider, please can you review if you have some problems with the new version?
Let me know the results of your test please
Xav-Pe
commented
3 years ago Hello, same error with 0.2.2. I included the output of terraform init and terraform plan below :
elsudano
commented
3 years ago Hi Xav-Pe,
Thanks for the last log, in that lines we can saw different points, If you compare the previous error with the last one you can see little bit differences.
Firstly in the previous error you can see that the error was reference at the unexpected SHA-256 hash, this is because you keep the file .terraform.lock.hcl in your folder of Terraform deploy.
In another hand, you can saw that the last error is because you haven't enable the API REST of the VmWare WorkStation in the moment that you doing the terraform apply
When you can saw plugin failed to exit gracefully it's mean that the puglin can't reached the VmWare API
Please can you confirm that ?
Another point here is the line:
2021-04-19T09:45:37.496+0200 [DEBUG] plugin.terraform-provider-vmworkstation_v0.2.2: .terraform/providers
/registry.terraform.io/elsudano/vmworkstation/0.2.2/linux_amd64/terraform-provider-vmworkstation_v0.2.2: /lib/x86_64-linux-
gnu/libc.so.6: version `GLIBC_2.32' not found (required by .terraform/providers/registry.terraform.io/elsudano/vmworkstation/0.2.2
/linux_amd64/terraform-provider-vmworkstation_v0.2.2)When I have tried reproduce the issue this error no appear in my tests
Maybe in the next version I could put a different message
Xav-Pe
commented
3 years ago Hello,
Thanks for your answer.
The REST API is running and I can use it with curl :
$ curl 'http://127.0.0.1:8697/api/vms/BKQ2TTNDOC2LGTNVH2317LBKLDI4ALDE' -X GET --header 'Accept: application/vnd.vmware.vmw.rest-v1+json' --header 'Authorization: Basic dG90bzpUb3RvMTIzNDUk'
{
"id": "BKQ2TTNDOC2LGTNVH2317LBKLDI4ALDE",
"cpu": {
"processors": 2
},
"memory": 2048
But with terraform (from a clean directory) it fails :
$ terraform plan
var.vmworkstation_url
URL de l'API REST
Enter a value: http://127.0.0.1:8697/api
var.vmws_reource_frontend_sourceid
(Required) The ID of the VM that to use for clone at the new
Enter a value: BKQ2TTNDOC2LGTNVH2317LBKLDI4ALDE
╷
│ Error: Could not load plugin
│
│
│ Plugin reinitialization required. Please run "terraform init".
│
│ Plugins are external binaries that Terraform uses to access and manipulate
│ resources. The configuration provided requires plugins which can't be located,
│ don't satisfy the version constraints, or are otherwise incompatible.
│
│ Terraform automatically discovers provider requirements from your
│ configuration, including providers used in child modules. To see the
│ requirements and constraints, run "terraform providers".
│
│ failed to instantiate provider "registry.terraform.io/elsudano/vmworkstation" to obtain schema: Unrecognized remote plugin message:
│
│ This usually means that the plugin is either invalid or simply
│ needs to be recompiled to support the latest protocol.I cleaned the directory (rm -rf .terraform .terraform.lock.hcl terraform.tfstate) and did a new log with terraform init and terraform plan :
But I think it's related to your glibc requierements:
[DEBUG] provider.terraform-provider-vmworkstation_v0.2.2: .terraform/providers/registry.terraform.io/elsudano/vmworkstation/0.2.2/linux_amd64/terraform-provider-vmworkstation_v0.2.2: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by .terraform/providers/registry.terraform.io/elsudano/vmworkstation/0.2.2/linux_amd64/terraform-provider-vmworkstation_v0.2.2)
On debian buster up-to-date, the glibc has the version 2.28.
$ ls -al /lib/x86_64-linux-gnu/libc.so.6
lrwxrwxrwx 1 root root 12 May 1 2019 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.28.soOn Ubuntu 20.04 LTS :
$ ls -al /lib/x86_64-linux-gnu/libc.so.6
lrwxrwxrwx 1 root root 12 Dec 16 12:04 /lib/x86_64-linux-gnu/libc.so.6 -> libc-2.31.soWhat are your requierments regarding distributions?
elsudano
commented
3 years ago Hi Xav-Pe,
Thanks for your detailed report, I have found a couple of things in it, you are using Terraform version 0.15, unfortunately, I have not yet tested my plugin with that version.
Other than that, I see that you are fill the variable values by hand, why are you not using a tfvars variable file?
additionally, if is possible for you maybe you can use the environment var export VMWS_DEBUG=true for Debug
In another hand, my project haven't requirements directly about of GLIBC version, but seems that when I compiled the binary file, GO language used my last version of this library, actually, I use a Manjaro distribution, with base in Arch Linux.
I will continue looking for errors to try to solve the problems it reports. I will keep you informed of the progress.
Greetings
elsudano
commented
9 months ago This issue was resolve in the latest version
https://registry.terraform.io/providers/elsudano/vmworkstation/latest
All the feedback will be welcome
Hello,
With this simple code, I have different behaviours depending on the version.
With
version = "0.1.9",terraform init -upgraderuns fine butterraform planyellsWith
version = "0.1.8",terraform init -upgradegets checksum errors :version = "0.1.7",terraform init -upgradeandterraform planruns fine but I have the issue #5Am I missing something, or is there any bugs?
I'm using Workstation Pro 16.1.0 build-17198959.