-
Notifications
You must be signed in to change notification settings - Fork 585
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
Chef installer permissions issue when using test-kitchen vagrant/virtualbox 16.04 #1406
Comments
I am unable to replicate this issue which at least tells me a few things about what is likely the cause. This means it's unlikely to be the box itself and more likely something related to the Host OS and shared folders. First thing I'd try is:
kitchen-vagrant, unlike most other drivers, allows for caching of the downloaded binary and serves it up over a shared folder. That said, shared folders are regularly a source of all manner of bizarre issues (symlinks break, permission weirdness, distro specific issues) so disabling them from the mix can be helpful. We only automatically enable this with bento boxes and only a subset of them that we are confident to be working in most scenarios. Try that and let us know how it goes! |
Thank you @cheeseplus. Your suggestion resolved the problem. I'm closing this as resolve. |
This also could be related to the Vagrant and VirtualBox versions being used so if you want to add those for posterity we can keep an eye out as this is the first time I've seen this kind of behaviour. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Chef install fails on Ubuntu16.04 in vagrant/virtualbox test kitchen.
Kitchen Version
ChefDK Version
Ruby Version
Platform Version
Replication Case
kitchen.yml:
Running
kitchen test
results in the failed chef download you can see in the output below. I've tried downgrading to test-kitchen version 1.20 with the same error. I was able to run my tests using the docker driver, but vagrant will not work.It's not clear to me if this is a problem with the permissions configured in the chef install.sh file, or the bento image. If there's something I'm missing, please let me know.
Here's the
/tmp
directory on the VM:Kitchen Output
Kitchen Diagnose
https://gist.github.com/AlexClineBB/3c54006d1c7cbe42b68d696d08b5a4dc
The text was updated successfully, but these errors were encountered: