Has anybody else ever been able to add a vagrant machine to a Juju controller with a command like this?
juju add-machine ssh:firstname.lastname@example.org
It just gets hung on this line in the trace logs:
16:42:20 TRACE juju.utils.ssh ssh_openssh.go:151 running: ssh -o "PasswordAuthentication no" -o "ServerAliveInterval 30" -i /home/vagrant/.local/share/juju/ssh/juju_id_rsa -i /home/vagrant/.ssh/id_rsa email@example.com sudo /bin/bash -c "/bin/bash -c \"\$(echo 'CnNldCAtZQp0bXBmaWxlPSQobWt0ZW1wKQp0cmFwICJybSAtZiAkdG1wZmlsZSIgRVhJVApjYXQgPiAkdG1wZmlsZQovYmluL2Jhc2ggJHRtcGZpbGUK' | base64 -d)\""
I’m kind of shocked at the fact that I can’t get a 100% clean Ubuntu 18.04 or 20.04 machine to add to a Juju controller using SSH. I’m not sure if there is something weird about my dev environment, but the connectivity is fine and everything and it’s a standardized Ubuntu image I’m trying to add so I don’t know what’s wrong. Does anybody understand what the above trace log is trying to do and why it might just hang indefinitely?
It’s killing my development environment because I have to deploy inside of VMS, but I have to be able to access the Juju machines from my host, which means I can’t use LXD for the Juju machines.