Closed gianarb closed 6 years ago
If you ssh into the guest, do you see the expected role files in the shared directory (from you example above this would be /tmp/vagrant-chef/d3ad2625603a35ce8bae7be4bb5052ef/roles
but will be different on subsequent runs)? If the role files are found, does the jenkins role properly parse?
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. 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.
I have probably a not standard use case between Vagrant and chef-zero. I have these folders in my project.
The root Vagrantfile is working fine and I am using this chef-zero configuration
I added another Vagrantfile in a subdir
jenkins/Vagrantfile
and I am using this configurationBut this second Vagrantfile is not working because chef return 404 for the jenkins's role. I am not using environment variables or similar, I am just doing:
Vagrant version
But it's not working also with Vagrant 1.9.1
Host operating system
MacOSX 10.10.5
Guest operating system
CentOS
Debug output
Expected behavior
My expectation is that it's going to work has usual when the Chef folders are in the same Vagrantfile's directory. I have another Vagrantfile located in the "standard" place and it's working fine.
Actual behavior
The directories are synchronized to the guest. I can navigate and read my roles but Chef is not able to find that role during the provisioning.
Thanks Gianluca