-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uploading certificates fails on Vagrant 2.2.4 with 'communicator.rb:319:in block (2 levels) in upload': undefined method `end_with?'.." exception #34
Comments
downgrading vagrant should work, v2.2.1 was working for me. Greater versions (between 2.2.1 - 2.2.4) not tested. |
Also getting this error. 2.2.1 fixes it as a temporary measure. |
Running into same issue Vagrant 2.2.4
|
+1 on Vagrant 2.2.4. |
Installing Vagrant 2.2.3 resolves. |
I have forked a new plugin that fix this issue. |
@Toilal My new best friend |
To work around error in williambailey/vagrant-ca-certificates#34
At the moment, I really need this plugin so I'll maintain my fork. You may open pull requests on my repository if you catch any issue or want to implement some enhancements. Of course it would be nice if the initial maintainer gives the key of this repository and associated ruby gem. |
@williambailey: are you looking for a new maintainer? This is such a useful tool, but having it be forked really could be annoying over time for the community. Would you be willing to pass over the torch to @Toilal? |
went into same issue - if you don't want to rebuild the plugin and reinstall, simply update the file directly on disk (in my case from ~/.vagrant.d/gems/2.6.3/gems/vagrant-ca-certificates-1.3.0/lib/vagrant-ca-certificates/action/install_certificates.rb), line 78: ...for me it worked well. |
Changing line 78 from: worked for me as well. Is there any plan to fix this in master or we should rely on patched forks? |
Uploading fails with the following exception:
==> vagrantTest: -- internal_ca.pem => /etc/pki/ca-trust/source/anchors/internal_ca.pem
C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:319:in
block (2 levels) in upload': undefined method
end_with?' for #Pathname:vagrant20190312-8148-ypv1o8 (NoMethodError)from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:334:in
block in upload' from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:743:in
block in scp_connect'from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:383:in
connect' from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:741:in
scp_connect'from C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/communicators/ssh/communicator.rb:304:in
upload' from C:/Users/Stelmasik_S/.vagrant.d/gems/2.4.4/gems/vagrant-ca-certificates-1.3.0/lib/vagrant-ca-certificates/action/install_certificates.rb:80:in
block in upload_certificate'....
Any ideas for a quick fix?
Thanks a lot in advance!
Sebastian Stelmasik
The text was updated successfully, but these errors were encountered: