Closed
Description
The pinned and outdated version of Ansible brought too much headaches and it seems it's easier to update Ansible rather than continue to put more workarounds.
Also my initial assumption was that it's a regression and but it's turned out that it was actually a fix for buggy behaviour that we use: ansible/ansible#29618
History:
- fc72d3b pinning has been introduced
- 59f05ef it broke our deploy (TravisCI: html5validator and rflint fail to install on prod branch #1020)
- ef4abbb it broke our deploy again (Ansible fails to stop monitoring: 'NoneType' object has no attribute 'read' #1089) and I had to apply a workaround
@asm0dey JFYI