Git module handling bitbucket's altssh subdomain

Archives Ansible Project
1

Hello everyone!

I trying to do a code checkout from one of my repositories, hosted at bitbucket.
Unfortunately, as you might know, the connection speed is not the best when it comes to BitBucket (surely Atlassian will make this better in the future).

Anyhow, they did a great job providing some instructions on how to use BitBucket via SSH: https://confluence.atlassian.com/display/BITBUCKET/Use+the+SSH+protocol+with+Bitbucket
From an average of 10KB/s, I now have an average of more than 100KB/s. So you see the importance of this for me.

First stop was of course http://docs.ansible.com/git_module.html

`

  • git: repo=ssh://git@altssh.bitbucket.org:443/dvaida/reponame/
    dest=/home/apps/www/mywebsite/current
    accept_hostkey=yes
    #key_file=/home/vagrant/.ssh/vagrant-ansible

`

So, I am forwarding my ssh agent successfully and I am able to see how the “.git” folder gets to the total size of the repository but the playbook doing the checkout task hangs indefinitely.

Another interesting thing is that the ‘known_hosts’ file on the VM has this if I do the checkout via the ‘shell’ module:

`
vagrant@wheezy:~$ cat ~/.ssh/known_hosts

1|m8ZlPHnV4PFu3pCjCDar3s0nvT0=|gS/aKzWEKuBqG6QiXGrTb2qYjck= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw==
1|XTtrBhy4makRwEyqrzniE00sP+E=|wJ8B+uYtJ4J2qWDD5GKdUVCPbE8= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAubiN81eDcafrgMeLzaFPsw2kNvEcqTKl/VqLat/MaB33pZy0y3rJZtnqwR2qOOvbwKZYKiEO1O6VqNEBxKvJJelCq0dTXWT5pbO2gDXC6h6QDXCaHo6pOHGPUy+YBaGQRGuSusMEASYiWunYN0vCAI8QaXnWMXNMdFP3jHAJH0eDsoiGnLPBlBp4TNm6rYI74nMzgz3B9IikW4WVK+dc8KZJZWYjAuORU3jc1c/NPskD2ASinf8v3xnfXeukU0sJ5N6m5E8VLjObPEO+mN2t/FZTMZLiFqPWc/ALSqnMnnhwrNi2rbfg/rd/IpL8Le3pSBne8+seeFVBoGqzHM9yXw==

`

But, when I try doing the checkout using the git binary on my local host, I get different entries in my ‘known_hosts’ file (after accepting the key prompt).

If required, I can run it with ‘-vvvv’ and also post the git-related running processes on the VM that’s doing the checkout.

Perhaps the problem is that the git module doesn’t like the ‘:443’ part in there. Didn’t had the time yet to study the module.

2

Sounds like you may wish to file a github ticket, or there is already a github ticket, as this is pretty familiar sounding. But it might have been from your twitter post.

If you still see this on the development branch, it may be worth filing one, or sending in a pull request to teach the known hosts detection logic what to do.