-
Notifications
You must be signed in to change notification settings - Fork 35
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
Error when trying to run the playbook #8
Comments
Should work now. LMK if you still see this on latest master. |
I changed it to dff125af04d93dc24e270645490fa414fe524be4a5136f8a16554c587033f9e3 (just to see what will happen). And it went through. |
@BobTB which version of Ansible are you on? |
ansible is version 2.9.6, python version 3.8.10 |
Should I try with 2.8? |
Got the same issue - tried ansible 2.9.0, 2.10.17, 2.12.2 - then found out that there are 2 issues:
|
Does it work for you then, or you stuck at the same place I am? |
Ok some update - during more code reviewing - I had actually found a working configuration (also on ansible [core 2.12.2]), did a pull request (#10) with the changes that fixed it for me - i was looking to run v 1.10 so had to add that also + here are my vars for the role that you may need to set to make it work:
I had to disable also cpu optimizer as I am deploying into Google cloud platform and they do not support changing these there... |
After changing to ansible 2.12.3 and applying your fixes, I got it running. great! Now I just have to setup it access to the outer world |
Appreciate the fixes and the trouble shooting - sorry was a hectic week last week!
|
the issue is that the default value for solana version is I could pr an update to the defaults to |
Fixes rpcpool#8 Use a version of the installer for which we have a checksum in `vars/main.yml`.
Fixes rpcpool#8 Use a version of the installer for which we have a checksum in `vars/main.yml`.
This is what I get when running anisble-playbook on a localhost. What am I missing?
The text was updated successfully, but these errors were encountered: