Hello,

The error is telling you that vagrant can't login.

Also is telling you is using vagrant user but no password

So, what is happing is:

You created the original box, and vagrant since 1.7.x it does change
the ssh key, from the known public one to a private one.

This new VM doesn't have the ssh key to login and is failing.

Options.
1.
In the first VM you need to use:
config.ssh.insert_key = false

this will avoid the change in the key

Before packaging/cloning you need to:

1.a ensure there is no /etc/udev/rules.d/70-persistent-net.rule
1.b there is no hardcoded UUID/MACADDRESS in the network configuration files
1.c the first nic is set to NAT
1.d ideally are not more nic configurations.

in your particular case I don't think you have an issue, since is
trying to connect, but just leaving these here just in case.

2.
tell vagrant user and pass

config.ssh.user = "vagrant
config.ssh.password = "vagrant"

password need to match the one for the VM



Can you check 1 and see how it goes?

Thanks

On Thu, Oct 22, 2015 at 7:08 PM, Stefaans Mostert
<[email protected]> wrote:
>
> Hi all
>
> I use vagrant-vshere to deploy.
> Now I clone the box from my base box.
>
> I use a
> vsphere.customization_spec_name = 'Vagrant1' (here I spesify an unused IP)
> and
> config.vm.network :private_network, ip:"10.1.212.2"
>
> now all goes well until.....
> Vagrant tries to ssh to that box.
>
> Ikeep getting this.
>
> DEBUG ssh: == Net-SSH connection debug-level log END ==
>  INFO ssh: SSH not up: #<Vagrant::Errors::SSHAuthenticationFailed: SSH
> authentication failed! This is typically caused by the public/private
> keypair for the SSH user not being properly set on the guest VM. Please
> verify that the guest VM is setup with the proper public key, and that
> the private key path for Vagrant is setup properly as well.>
>
> Now as I have it in Vagrant 1.7 (I use 1.7.4) it creates it's own unique
> key?
>
> After a reboot the ip has changed.
>
> Now I get this error
>
> DEBUG ssh: == Net-SSH connection debug-level log END ==
>  INFO retryable: Retryable exception raised: #<Timeout::Error: execution
> expired>
>  INFO ssh: Attempting to connect to SSH...
>  INFO ssh:   - Host: 10.1.212.2
>  INFO ssh:   - Port: 22
>  INFO ssh:   - Username: vagrant
>  INFO ssh:   - Password? false
>  INFO ssh:   - Key Path: ["/home/user1/.vagrant.d/insecure_private_key"]
>
> Now it did not set my default gateway properly, I added that.
>
> Now I get the first error again.
>
> In debug it sees that vagrant is not using vagrant or no passwd as a
> password to ssh in?
> INFO ssh:   - Username: vagrant
>  INFO ssh:   - Password? false
>
> This is driving me nuts!!
>
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/4236fe32-8c4a-4478-9092-29f92a61961e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eywgORry8TKOtYD6jMV%3DrMpmw1Z8FkBeHA3X7fYYq-zNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to