Closed ksclarke closed 6 years ago
@bess pointed out an ansible-samvera update that I hadn't yet pulled down: https://github.com/curationexperts/ansible-samvera/blob/master/roles/capistrano_setup/tasks/main.yml#L64-L66
Getting in sync with the upstream ansible-samvera solved the issue. It's good to learn one possible underlying cause of that no tty present
error too since I've seen them off and on while working with / learning Ansible.
An upgrade to samvera-mgmt code yields the following from:
name: deploy to production directories with capistrano shell: cap -p --trace=stdout {{ cap_deployment }} deploy