Hi
$ vagrant ssh-config
Host default
HostName 127.0.0.1
User vagrant
Port 2200
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile /mnt/c/temp/.vagrant.d/insecure_private_key
IdentitiesOnly yes
LogLevel FATAL
On Wednesday, September 30, 2020 at 3:52:10 PM UTC-5 brae...@gmail.com
wrote:
> On 9/30/20 10:36 PM, Keith Mills wrote:
> > Hi Dick
> >
> >
> > Ran vagrant ssh in WSL2.
> >
> >
> > So then I tried using raw SSH:
> >
>
> What does "vagrant ssh-config" say?
>
> Regards
> Racke
>
> >
> >
> >
> > On Tuesday, September 29, 2020 at 9:57:38 AM UTC-5 dick....@geant.org
> wrote:
> >
> > On Tue, 29 Sep 2020 at 15:19, Keith Mills <mills....@gmail.com> wrote:
> > >
> > > Hello All,
> > >
> > > Running ansible but keep getting failed to connect to host via ssh.
> > >
> > > Vagrant Version: 2.2.10
> > >
> > > Host OS: Windows 10 (+ virtualbix)
> > >
> > > Guest OS: bento/ubuntu-18.04
> > >
> > > WSL version: 2
> > >
> > > Vagrantfile:
> > >
> > > Vagrant.configure("2") do |config|
> > > config.vm.box = "ubuntu/trusty64"
> > >
> > > config.vm.synced_folder ".", "/vagrant", disabled: true
> > >
> > > config.vm.provider "virtualbox" do |vb|
> > > vb.memory = "4024"
> > > vb.cpus = "1"
> > > end
> > >
> > > config.vm.provision "ansible" do |ansible|
> > > ansible.become = true
> > > ansible.verbose = "v"
> > > ansible.playbook = "roles/firewall.yml"
> > > ansible.galaxy_roles_path = "./roles"
> > > end
> > > end
> > >
> > > Expected behavior:
> > >
> > > Successful provision
> > >
> > > Actual behavior:
> > >
> > > TASK [Gathering Facts]
> *********************************************************
> > > fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to
> connect to the host via ssh: ssh: connect
> > to host 127.0.0.1 port 2222: Connection refused", "unreachable": true}
> > >
> > > Steps to reproduce:
> > >
> > > 1. minimal firewall.yml file
> > > 2. vagrant up --provision
> > >
> > >
> > > I tried:
> > >
> > > 1. Run vagrant up in PowerShell
> > > 2. Run vagrant ss in WSL2
> > >
> > >
> > > But nothing happens:
> > >
> > >
> > >
> > > So then I tried using raw SSH:
> >
> > And then the message was cut short...
> > Please send the rest of the text (not images/screendumps please).
> >
> >
> > --
> > Dick Visser
> > Trust & Identity Service Operations Manager
> > GÉANT
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Ansible Project" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to
> > ansible-proje...@googlegroups.com <mailto:
> ansible-proje...@googlegroups.com>.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/ansible-project/d585cc97-481c-49be-a6a7-1374b20c6db0n%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/ansible-project/d585cc97-481c-49be-a6a7-1374b20c6db0n%40googlegroups.com?utm_medium=email&utm_source=footer
> >.
>
>
> --
> Ecommerce and Linux consulting + Perl and web application programming.
> Debian and Sympa administration. Provisioning with Ansible.
>
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/da765d49-f7db-4aa9-b80c-eba20cbdc91dn%40googlegroups.com.
