-
Notifications
You must be signed in to change notification settings - Fork 49
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
Ansible provider version incompatible with linux_amd64 | Empty Summary: This is always a bug in the provider #126
Comments
+1 as I am running into the exact same issue now. Has been working for months and stopped working. I am runnning it in an Ubuntu container |
This error weirdly dispeared on ubuntu (did nothing just rerun the pipeline)
So just bumping ansible version to 1.3.0 on ubuntu is good now. |
I have the same problem. I was using version 1.1.0 for a few months but recently i got the error that the provider is not available for my platform linux_amd64. Updating to version 1.3.0 did not fix it for me on ubuntu 22.04. |
same for me |
I have been using Ansible provider for 8 months, version is 1.1.0. It works well until yesterday I run the pipeline and got the error when
terraform init
Error: Incompatible provider version│ Provider registry.terraform.io/ansible/ansible v1.1.0 does not have a│ package available for your current platform, linux_amd64.
(Nothing has changed on my code) 1.2.0 has same errors as 1.1.0.Found that 1.3.0 been published 14 days ago, the last time I run the pipeline is 15 days ago working well.
After bump ansible provider version to 1.3.0,
terraform init
is good, butterraform plan
error logs are:Error: Empty Summary: This is always a bug in the provider and should be reported to the provider developers.
( Same errors with TF_LOG=DEBUG).ansible_vault is the only resource used in my case.
Then I ran terraform init & plan locally on my local (Mac M1 arm64) with 1.3.0, it works well.
Here's my local terraform version:
Terraform v1.5.6 on darwin_arm64
Changing pipeline pool from ubuntu to Macos works for now.
Can somebody help with that? Thank you.
The text was updated successfully, but these errors were encountered: