juju snap, ssh-agent not consulted

[David Britton]

Notice the two passphrases that I needed to enter:

dpb@helo:~[0]$ juju bootstrap costack costack
Creating Juju controller "costack" on costack
Looking for packaged Juju agent version 2.0.1 for amd64
Launching controller instance(s) on costack...
 - node-0b846b36-18b0-11e6-9843-00163eef97fa (arch=amd64 mem=4G cores=2)
Fetching Juju GUI 2.2.3
Waiting for address
Attempting to connect to 10.5.0.3:22
Enter passphrase for key '/home/dpb/.ssh/id_rsa':
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Enter passphrase for key '/home/dpb/.ssh/id_rsa':
Warning: Permanently added '10.5.0.3' (ECDSA) to the list of known hosts.
Logging to /var/log/cloud-init-output.log on the bootstrap machine
Running apt-get update
Running apt-get upgrade
Installing curl, cpu-checker, bridge-utils, cloud-utils, tmux
Fetching Juju agent version 2.0.1 for amd64
Installing Juju machine agent
Starting Juju machine agent (service jujud-machine-0)
Bootstrap agent now started
Contacting Juju controller at 10.5.0.3 to verify accessibility...
Bootstrap complete, "costack" controller now available.
Controller machines are in the "controller" model.
Initial model "default" added.

I have an ssh-agent running and in my environment, but the snap version is not using it for some reason:

dpb@helo:~[0]$ snap list juju
Name Version Rev Developer Notes
juju 2.0.1 281 juju devmode

[Nicholas Skaggs (nskaggs)]

Thanks for this feedback David. It's not clear yet if this is something we can change within the snap, or if we need something additional from snapd. I too am surprised this is happening under devmode truthfully; though we know we need better SSH support under strict mode.