-
-
Notifications
You must be signed in to change notification settings - Fork 268
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 recipe for python causing "vagrant up" to fail #566
Comments
@ryanjarvis You are right! The requirement swig is not installed and that's why is failing. I'm fixing it right now! I'll keep you posted. Thanks a lot for reporting the issue! |
Can you try again after pulling the changes? Please, let me know if it is fixed or not. After this fix, I've tried again and it worked. |
Thanks for the quick response, but no this hasn't fixed my problem yet. The above error is being thrown at line 33 of /cookbooks/python/recipes/pip.rb This is the python recipe not the pybossa recipe, which, as far as I can understand, gets processed first. Is there a full log or stacktrace I could give you somehow? |
Hi, Sorry to hear that it is not fixed. The pip recipe as you have said it is a different one and I'm using the defaults, so maybe there is something broken there, however why did it worked for me? You should get a full error in the terminal, can you copy and paste the error here? It will be also good if you can open an issue in the pip cookbook so the authors can review it. Cheers, Daniel |
Here is the exact output I get when I clone the pybossa repo and call vagrant up:
|
Hi, interestingly now I'm getting an error, not in pip, but when installing the requirements of Flask-Babel. According to the output error it cannot find the right version for pytz package, which is strange as it works outside the VM. I'm checking it. Regarding your issue: it seems like this has happened before. Can you try to upgrade in your copy to the latest python cookbook and try again? |
Hi again, I found the problem. With the current set up, vagrant chef cookbook for python installs pip 1.4 which is incompatible with pytz. I'm looking for a fix :-) |
What version of Vagrant are you using? I am using 1.2.4. The fact that we are getting different errors suggest to me we aren't using the same tools. I downloaded the latest Opscode Python cookbook and I still get the same error. I found this issue: https://groups.google.com/forum/#!topic/vagrant-up/vJbAT6iWlt8 |
Hi, Good point! I'm with version 1.2.2. Can you install version 1.2.2 to see if the version is the problem? |
The plot thickens... Below is my log showing a new error when I use Vagrant 1.2.2. Everything provisions except for Pybossa. Long story short: your first call to create a python virtual environment fails for me. I went ahead and googled "virtualenv protocol error" and I found a couple links that might help you figure out what to do:
|
Hi, I don't know why is failing to create now the virtualenv. Can you completely destroy the vm and try again? You can even remove your .vagrant.d folder in your home directory (if you are in GNU/Linux) to start from scratch. Copy that folder to another location, to have a backup. Let me know what happens. I'll try to test it in another system, as it is working for me really. Question: which VirtualBox are you using? I'm using 4.2.16. |
The issue is probably because I am building everything on a Windows machine. The links in my last post suggest two things:
Because /vagrant/vagrant_env is a shared folder, it will follow the rules of the host operating system that you are using Vagrant/VirtualBox on. If you are building your project on a GNU/Linux system, you won't see my error since your host operating system supports sym links. However, since I am building on a Windows box, you won't be able to add sym links to /vagrant/vagrant_env. (which is what virtualenv is trying to do on line 5 of your pybossa.rb recipe) So the way I see it, you have two solutions:
If you do not have access to a Windows machine, I am happy to be your guinea pig. Perhaps you should set up a branch for Windows testing. |
Oh and yes I am using VirtualBox 4.2.16. And am also building on Windows 7, which I probably should have stated at the start of this conversation. :-) |
Ok, I got it to work. I can confirm that changing the directory that you install python virtualenv solves the problem. (I had it install in /opt/python) Once that happens, Chef completes all recipes successfully and you have Pybossa in a VM. I would submit a pull request, but I don't know if you want to use my solution or not. |
Hi, Thanks for confirming the solution, and yes I like your solution. Please, test this branch which has the fix. If it works for you, in Linux works, I'll merge it. Next time, just send the pull-request ;-) |
Closing it, as the pull requests works again. |
Found this on google... The reason for the failed symlink is not because the mounted dir was on windows, but because you cannot symlink into a remote mount regardless of the OS. |
+1 @mkoryak Now it is fixed and running :-) |
When attempting to run "vagrant up" and having the virtual machine build, the python recipe fails when attempting to install pip.
The text was updated successfully, but these errors were encountered: