Reusing previous version of multani/libvirt from the dependency lock file
Using previously-installed multani/libvirt v0.6.3-1+4
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
kkadmin@Node1:~/terraform$ terraform apply
╷
│ Error: Failed to load plugin schemas
│
│ Error while loading schemas for plugin components: Failed to obtain provider schema: Could not load the schema for provider
│ registry.terraform.io/multani/libvirt: failed to instantiate provider "registry.terraform.io/multani/libvirt" 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...
kkadmin@Node1:~/terraform$ terraform version
Terraform v1.1.7
on linux_amd64
christrt9
commented
2 years ago
terraform init
Initializing the backend...
Initializing provider plugins...
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work.
If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary.
kkadmin@Node1:~/terraform$ terraform apply ╷ │ Error: Failed to load plugin schemas │ │ Error while loading schemas for plugin components: Failed to obtain provider schema: Could not load the schema for provider │ registry.terraform.io/multani/libvirt: failed to instantiate provider "registry.terraform.io/multani/libvirt" 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...
kkadmin@Node1:~/terraform$ terraform version Terraform v1.1.7 on linux_amd64