Closed onknows closed 6 years ago
@onknows Hmm, does this work if you use a full path rather than a relative path?
Yes it works with full path. This is the workaround I'm using now.
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.
Please note that the Vagrant issue tracker is reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list: https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
2.0.1
Host operating system
Ubuntu 16.04
Guest operating system
Ubuntu 16.04
Vagrantfile
Debug output
https://gist.github.com/onknows/305dfe8a2b6a3517ac2a3879961ebe40
Expected behavior
vagrant up with Chef provisioning works similar to 1.8.7
Actual behavior
vagrant up does not work and returns Path specified for
nodes_path
does not exist: ["~/chef/nodes"]Steps to reproduce
References