ansible-modules-core

Definitely agree with this. I use the docker module extensively and found 2 regressions[1][2] that I went through the trouble of debugging down to a single commit, but still have no idea whether anyone is going to fix them. I'm hoping now that they are done rewriting the docker modules, and considering they are using docker as a selling point for 2.1, they will be more proactive with these issues. 1. https://github.com/ansible/ansible-modules-core/issues/3219 2. https://github.com/ansible/ansible-modules-core/issues/3231

It is unfortunate that Ansible has a complete lack of test cases around core modules and, as a result, people act surprise when they're broken in a new release. For example see this fairly critical defect with the s3 module in today's release: https://github.com/ansible/ansible-modules-core/pull/3347

I also had this problems in the past with SNI certs. Very annoying old python bug, it's possible to fix old python but this makes no sense for an Ansible deployment http://stackoverflow.com/a/29099439/756056 Better approach: Use curl to download in some temp directory/file and then extract from there. Curl does not have this errors. Example: https://github.com/ansible/ansible-modules-core/issues/1716#... My dream would be that whole Ansible would use rockstable libcurl instead of the requests library which has problems with Certs on (not so) old python versions.

Revert your playbooks and roles to the version of your last good deployment, and redeploy. With good version control, role version management and idempotent library modules, this should be functionally equivalent to a rollback. There are plenty of caveats to the above (like the fact that the yum module won't downgrade [1], and you'll need reversible DB migrations) but that's basically the procedure. [1] https://github.com/ansible/ansible-modules-core/issues/1419

Bad maintainers will rejoice at the possibility of replicating a fiasco like this: https://github.com/ansible/ansible-modules-core/pull/2023 with zero effort. Saved replies are a silver bullet only for those who already took the time to compose meaningful (engaging?) replies. For all the others, a quick way to shoot themselves in their feet.

interesting alternative if you have a decent python version! However I need to say that Python+request lib has historically bugs (which are resolved in newer python 2.7.9+ versions). For example I had problems with SSL SNI certificates with older python versions and CURL and WGET don't have this problems on older Linux distributions. Last year I also had a lot of headache because of this in Ansible (Python + request lib based): https://github.com/ansible/ansible-modules-core/issues/1716#... So I bet more on curl than python+request lib

Quite funny, but I had an experience with Ansible that's similar to the one the other commenter had with Drupal. I have a very trivial pull request[0] which I have been trying to get reviewed & merged since March. It's only around 20 lines of code, but I've been asked to rebase it due to merge conflicts multiple times. I did so, but nothing came out of it on either of those occasions. [0]: https://github.com/ansible/ansible-modules-core/pull/901

I attempted to do something like this when figuring out our build problems but it didn't really work for me. It doesn't solve the problem of actually getting configuration into the build very well because it still relies on Dockerfiles and has the added side effect of making the cache mostly useless. Maybe I was just doing it wrong? I also attempted to try Ansible for deploying containers and had issues with both of these bugs: https://github.com/ansible/ansible-modules-core/issues/27 https://github.com/ansible/ansible-modules-core/issues/188 Do people actually use Ansible to control Docker in practice? It would be great to have something that was a step up from building random Python scripts from scratch :) (Disclaimer: I'm not very good at Ansible.)