jlund
commented
7 years ago Streisand does set up droplets so that they can be accessed via SSH (that's how Ansible connects to servers to configure them), but it looks like there is a permission error with your /home/test/.ssh/id_rsa file. That's why you have to fall back to password-based authentication in order to connect.
You probably just need to ensure that the permissions on that file are set correctly. Something like this should work:
sudo chown test:test /home/test/.ssh/id_rsasudo chmod 600 /home/test/.ssh/id_rsa
You can test whether or not things are set up correctly by creating a new Droplet via the DigitalOcean Control Panel. Select the streisand SSH key when creating the server, and then attempt to connect to it over SSH. If you're still prompted for a password, there's a problem with your SSH configuration, SSH agent, or SSH key somewhere in the chain separate from Streisand. If it works, you should be ready to try running Streisand again. The end result will be better once SSH is fully working on your system :)
Let me know if I can help you troubleshoot further!
zabcheckmate
Below are the results from running streisand:
S T R E I S A N D
Which provider are you using?
What region should the server be located in?
What should the server be named? Press enter for default (streisand). [streisand]:
New API access tokens can be generated in the DigitalOcean control panel. https://cloud.digitalocean.com/settings/applications
If this field is left blank, the environment variable DIGITALOCEAN_API_KEY will be used.
What is your DigitalOcean Access Token? : [Redacted]
The following information can be found on your DigitalOcean control panel. https://cloud.digitalocean.com/settings/security
What is the name of the DigitalOcean SSH key that you would like to use?
DigitalOcean requires SSH keys to be unique. You cannot upload multiple keys that have the same value under different names.
If you see an error that says 'SSH Key failed to be created' once the setup process starts, then this is the problem. You can retry the setup process using the name of the existing SSH key from the DigitalOcean control panel that matches the contents of your RSA public key. [streisand]:
Streisand will now set up your server. This process usually takes around ten minutes. Press Enter to begin setup... :
PLAY [Provision the DigitalOcean Server] ***
TASK [setup] *** ok: [localhost]
TASK [genesis-digitalocean : Set the DigitalOcean Access Token fact to the value that was entered, or attempt to retrieve it from the environment if the entry is blank] *** ok: [localhost]
TASK [genesis-digitalocean : Get the default SSH key] ** changed: [localhost]
TASK [genesis-digitalocean : Add the SSH key to DigitalOcean if it doesn't already exist] *** changed: [localhost]
TASK [genesis-digitalocean : Create the new Droplet] *** changed: [localhost]
TASK [genesis-digitalocean : Wait until the server has finished booting and OpenSSH is accepting connections] *** ok: [localhost]
TASK [genesis-digitalocean : Create the in-memory inventory group] ***** changed: [localhost]
TASK [genesis-digitalocean : Set the streisand_ipv4_address variable] ** ok: [localhost]
TASK [genesis-digitalocean : Set the streisand_server_name variable] *** ok: [localhost]
PLAY [Checking instance status] ****
TASK [Wait for cloud-init to complete] ***** fatal: [[Redacted]]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '[Redacted]' (ECDSA) to the list of known hosts.\r\nLoad key \"/home/test/.ssh/id_rsa\": Permission denied\r\nPermission denied (publickey).\r\n", "unreachable": true} to retry, use: --limit @/home/test/streisand/playbooks/digitalocean.retry
PLAY RECAP ***** [Redacted] : ok=0 changed=0 unreachable=1 failed=0
localhost : ok=9 changed=4 unreachable=0 failed=0
I'm fairly new to this, so apologies if I missed something basic, but I do see the "streisand" droplet and the "streisand" ssh key on my DO account. I tried accessing the droplet from the terminal with "ssh -i ~/.ssh/id_rsa root@[Redacted]" and got:
Load key "/home/test/.ssh/id_rsa": Permission denied root@[Redacted]'s password:
This surprised me as I thought streisand set up droplets so that they could just be accessed by ssh, but I wasn't sure. If I reset the root password on DO, I can access the droplets this way, but I still can't seem to get the streisand process past this step without this error. Thanks!