Vagrant-virtualbox ssh authentication for CDK installation

[ephriam.toh]

I am installing CDK using the kit for windows. Each I run the following command:

C:\DevelopmentSuite\cdk\components\rhel\misc\shared_folder\rhel-ose>vagrant up, I have this error message:

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Machine already provisioned. Run `vagrant provision` or use the `--

provision`

==> default: flag to force provisioning. Provisioners marked to run always will

still run.

==> default: Running provisioner: shell...

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.

Any help?

Regards

[doh]

There are a number of provisioning steps performed when Vagrant launches a virtual machine. These may come from plugins, such as the Vagrant Registration plugin for Red Hat, or from steps that are included in the Vagrantfile for provisioning the box on startup. Vagrant runs these commands by using SSH.

In many cases, errors during the provisioning step are not fatal, so the Vagrant box will still be running. Use the vagrant status command to see what the state of your box is. You can stop the Vagrant box with the vagrant halt command. If the machine is running, you should be able to log into it using the vagrant ssh command to examine the VM and see what went wrong.

While the box is running, you can rerun the provisioning steps by running the vagrant provision command.

Note that you need to be in the same directory where your Vagrantfile is. If you have lost track of where your Vagrantfile is, use the vagrant global-status command to list the boxes that you have started and the directory where the Vagrantfile and state is stored.

[lalatendum]

Are you using Vagrant version 1.5.0 as it is a known issue in that version of Vagrant. Please use Vagrant version mentioned in the  "Vagrant compatibility matrix" in CDK documentation.

[1]  https://access.redhat.com/documentation/en/red-hat-container-development-kit/2.2/paged/release-notes-and-known-issues/ch…