-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
vagrant up throws an error (already tested everything) #10511
Comments
Hello @eyemiru - do you still have this problem if you comment out your puppet provisioner? |
Just tested it. Same error. |
Hi @eyemiru - this is a different error:
|
Yep. Now SSH works without puppet provisioner and npm. Any idea how I can debug this? |
@eyemiru The guest does not have the npm tool installed as can be seen by the stderr output:
You'll need to install npm on the guest for the provision script to succeed. Cheers! |
Yeah, npm is not the issue. It's rather the puppet provisioner. |
Hello @eyemiru - thanks for opening an issue, but this seems to be a potential issue with your puppet manifest. This issue tracker is strictly for bugs with Vagrant. I recommend either emailing the Vagrant up mailing list which might be able to provide support. Otherwise if there's an issue with your puppet code I recommend looking up the way to get support from them, thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Vagrant version
2.2.2
Oracle version
5.2.22r126460
Host operating system
Windows 10 Pro (64 Bit)
Guest operating system
CentOS 7 / Debian
Vagrantfile
Debug output
https://gist.githubusercontent.com/eyemiru/689097744bf83cabcedbbbd5c9b94978/raw/97d605a5a4532f92c3342d55fac08de3f7b8efc9/gistfile1.txt
Expected behavior
SSH should work properly.
Actual behavior
SSH connection won't work. Worked 3 weeks ago and tried everything explained in several issues.
Error: The following SSH command responded with a non-zero exit status.
Steps to reproduce
References
See also: #1659
The text was updated successfully, but these errors were encountered: