It is not actually, in my investigation, coming from an Ansible default.
There's code inside the Galaxy role that tries to figure out which user to
use for remote_user (the one used in SSH) and when it is run with `become:
true` ends up incorrectly choosing root. However people more knowledgeable
t
Anything attempting to login remotely as root must be rejected. Peter's
policy approach is good for that. Most modern linices will not allow a
remote root login, which is correct. There are SSH ways to accomplish the
same thing, but depend on trust at both ends. The defaulting by Ansible is
rep
Hi there
I found I had this problem too, when the `become: true` applied to the
whole Galaxy play. My current top level playbook (at
https://github.com/pvanheus/masters_galaxy_ansible/blob/master/galaxy.yml#L25)
now applies `become: true` as it is needed, and does not apply it to the
`galaxyprojec
