Beginner: Looks like vagrant issue

[STARFISH]

Hi,

I created the setup of “vagrant with cent OS”.

When I do configuration, I could see the below error after done with “ping” command.

[root@localhost ansible]# ansible example -m ping -u vagrant
localhost | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh.",
    "unreachable": true
}
[root@localhost ansible]#

My configuration file is like this:

## db-[99:101]-node.example.com
[example]
localhost

and my hostname is like this

[root@localhost ansible]# hostname
localhost.localdomain
[root@localhost ansible]#

I had a comment from "ansible" groups, stating that this might be a "vagrant" issue.

Can you help me of fixing htis?

[Alvaro Miranda Aguilera]

hello

it looks more a ansible question rather vagrant, itsnt?

How the root user is being able to log in as vagrant?

did you setup root -> vagrant ssh password less?

Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/7fada917-5087-410c-8887-63bd11a50fe2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pixel fairy]

Can we see your vagrant file?

[STARFISH]

Below is my Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "bento/centos-6.7"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   sudo apt-get update
  #   sudo apt-get install -y apache2
  # SHELL
end

[Chris Roberts]

This looks like it might be an issue with the ssh key insertion. It's a fixed bug but hasn't been released yet. You should be able to work around it by adding this to your Vagrantfile:

config.vm.insert_key = false

Then do:

vagrant halt --force

vagrant destroy

vagrant up

Please let me know if that doesn't work for you.

Cheers!

--

This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6aa813aa-8b9e-4e3a-b5a4-9cda6b5d646d%40googlegroups.com.

[Ramesh]

Im getting the below error while doing.

Rameshs-MacBook-Pro:centos-6.7 Ramesh$ vi Vagrantfile
Rameshs-MacBook-Pro:centos-6.7 Ramesh$ vagrant halt --force
==> default: Discarding saved state of VM...
Rameshs-MacBook-Pro:centos-6.7 Ramesh$ vagrant destroy
    default: Are you sure you want to destroy the 'default' VM? [y/N] y
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The following settings shouldn't exist: insert_key

​

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/pwIvQ1TsQw0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CANhAuoC3PqHP78b5SY_15i%2B5CyB-36839oRR6yrBvzTM%3DQsziQ%40mail.gmail.com.

[Chris Roberts]

My apologies! It was a typo on my part. The line should read:

config.ssh.insert_key = false

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CABoYeGFtEXbBwfYksGZ%2Bcy2rpADpV-LzfiDjWdCjJt%2B53pE2OA%40mail.gmail.com.