-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Running Playbook - no filter named 'items2dict' #662
Comments
What version of Ansible are you using? What commit of the playbook? You should be able to start the services manually on the server with something like |
@aaronraimist , these were helpful questions that lead us towards a solution that ended up working. Thank you. We have everything running and working with the current commit of the playbook, right now.
I want to highlight this for anyone that is encountering this, as it may be easy to overlook due to the fact that prior docker image meets the Ansible version requirements, but I guess something isn't fully set in the container for newer updates to the playbook Appreciate all the work that everyone put in the Playbook. It is hard to imagine trying to set up all this ourselves (none of these particular languages and environments are in our team's wheelhouse). |
Interestingly, no one has reported this failure before #662 (Github Issue). It doesn't make sense to keep saying that we support such old Ansible versions, when we're not even testing on anything close to those. Time is also passing and such versions are getting more and more ancient. It's time we bumped our requirements to something that is more likely to work.
I imagined that the playbook required However, looking at the Ansible documentation here, it seems like We only use these filters in a few non-critical places right now:
I'm guessing we should either replace this with something else or bump the version requirement to v2.7. I've bumped the version requirement to v2.7 in 23daec7. Thanks for reporting this issue! 👍 |
We have used this Playbook to install Matrix Synapse / Riot nearly a year and a half-ago. Had everything working fine, and had even made multiple updates through the Playbook in following months.
However, it has been some time since running the playbook, and we have tried to run it now, but it has been unsuccessful. There were a number of minor things that we needed to do (changing dashes to underscore, host_vars to vars, etc.) and we are able to run the playbook as intended.
However we keep running into this problem and the Playbook just fails and now our Synapse service is down, and we are not able to back up our DB either. I try to avoid raising an issue just for the aspect of troubleshooting or supporting my problem; however, after trying various things over several days, it does seem to me that this is an actual issue of the Playbook (or at-least the documentation on how it should be run). As this occurs, just following the instructions as is.
It seems like this is related to maybe some kind of dependency not loading? (I don't know too much about ansible):
Any insights would be appreciated. More-so, however, I think this is important to note as an issue.
I would like to note that there is no references to Riot in any of our Vars; however, I don't think this is the issue as the actual intended task is failing (not giving the message it should if the check itself is running correctly)
The text was updated successfully, but these errors were encountered: