ssh agent and ansible 12 prompting incessantly

Question

I've been using the SSH Agent in 1Password for a couple of years now, with very little trouble. This includes lots of SSH to individual machines as well as a fair amount of ansible scripting using versions prior to 12 and run directly from Terminal. Recently, I did a `brew upgrade` and ended up with Ansible 12. After that, it has become commonplace that ansible scripts run on my local machine and talking to nearby devices over the network result in 1passwd SSH agent prompting for every...single...command.

I rolled back to ansible 10 (11 not available directly in Brew any longer) and the behavior returned to normal: prompting at the outset of my ansible script and not again until the next time I run a script.

Running Ansible (as opposed to directly sshing in Terminal) has always prompted at the run, and usually for each individual destination machine, but that has been it. With the change to Ansible 12, the prompting from the SSH agent in 1password is now such that it is not usable.

For the time being, I can roll back to ansible 10, but that won't be the case forever.

Does anyone else have experience with this? Any recommendations for either diagnostics or solutions other than just disabling 1password's otherwise-highly-useful SSH Agent?

gaigeb · Accepted Answer

So, after months of using a rolled-back version, I sat down to do some further diagnosis on this after realizing that it was only happening with one set of Ansible playbooks. In the end, the problem was a change in how Ansible lazily evaluates some variables. In my case, for these playbooks, I needed to use sudo, which required a password which was pulled from 1password. That was being evaluated for every single step that used become (which in this playbook was most of them).

The solution in my case was to pre-fetch the values from 1password early in the playbook using set_fact, which reduced the number of fetch requests to one for the playbook and I'm now able to move forward again.

Nice to know the problem (at least in my case) wasn't the SSH agent at all. Took quite some time to track this down, but eventually I was monitoring the SSH connections and they were clearly being reused, which was a strong indication it wasn't the agent being pinged separately.

ar4743 · Answer

I have same problems, I tried ansible 11 ansible-core==2.18.5 and ansible 10 ansible-core==2.17.6. It works OK, but when I install ansible 12 ansible [core 2.19.3]. I hade problems with promoting 1password every time.
Does anyone have any solution for it? For now I'm using ansible 11

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded