Vagrant 1.8.6 ?

31 August 2016 · Filed in Development

Like most of my team, I use vagrant to run local boxes for development of puppet builds, ruby apis and such like.

I recently upgraded my Windows workstation to vagrant 1.8.5 and immediately ran into an issue.

default: Inserting generated public key within guest...

default: Removing insecure key from the guest if it's present...

default: Key inserted! Disconnecting and reconnecting using new SSH key...

default: Warning: Authentication failure. Retrying...

default: Warning: Authentication failure. Retrying...

This monkey of an issue had me stumped for a while, as on another project, I was working with securing ssh logins to hosts on AWS, which made me suspect my id_rsa key setup under the git BASH.

My sanity has been saved by the admission of a bug on the vagrant issues list https://github.com/mitchellh/vagrant/issues/7610

A swift edit of the C:\HashiCorp\vagrant\embedded\gems\gems\vagrant-1.8.5\plugins\guests\linux\cap\public_key.rb file (line 58) and all is good again.

@@ -54,6 +54,7 @@

             if test -f ~/.ssh/authorized_keys; then

               grep -v -x -f '#{remote_path}' ~/.ssh/authorized_keys > ~/.ssh/authorized_keys.tmp

               mv ~/.ssh/authorized_keys.tmp ~/.ssh/authorized_keys

+              chmod 0600 ~/.ssh/authorized_keys

             fi
             rm -f '#{remote_path}'

The easier fix is to head over to downloads where it is hoped that 1.8.6 will be released on 1st September 2016.

 

Previous Post: Docker cleanup Next Post: AWS User Group North Sept 2016 Tags: vagrant

Recent Posts