I ran through the bedrock installation docs yesterday, got puppet errors doing `vagrant up`. When I did `vagrant ssh` and tried to re-run the puppet command inside the VM, it turned out puppet was barfing because mysql_client wasn't installed on the VM. After installing mysql_client, I did a trial `vagrant halt && vagrant up` and puppet ran without errors. If you can install mysql_client in the VM, I think first run will go cleanly. It's not clear how I could make this change, or I'd submit a patch :-) FWIW, I'm on late 2012 retina MBP, OS X Mavericks, Vagrant 1.2.5, Virtualbox 4.2.18.  https://pastebin.mozilla.org/3680423
Ah looks like mysql was added to the bedrock requirements but the vagrant install was not updated. I will look into fixing.
Assignee: nobody → booboobenny+bugzilla
I've made an attempt to fix this, along with some Vagrantfile issues: https://github.com/christi3k/bedrock/commit/13b230597c9f187e497b8716049b1ad09051c4ba Would someone try it out and let me know if it works? In particular, I want to make sure it still works on Vagrant 1.2.5 since I'm on 1.4.0.
Sure, I can test. Thanks for taking this! I cherry-picked 13b2305 into my copy of bedrock and I'm waiting for `vagrant up` to do its thing now. I'm on vagrant 1.2.5, macos 10.9, virtualbox 4.2.18.
Yup, looks like I can vagrant up without encountering any errors. Nicely done! I'll leave this bug open so bedrock devs can review the Vagrantfile and puppet changes and handle the merge.
Vagrant up works ok but running the full install, the sites do not render: http://bedrock.readthedocs.org/en/latest/vagrant.html I will try to track down the issue later today. This is not unexpected, changing vagrant versions often causes compatibility problems.
(In reply to Ben (:bensternthal) from comment #5) > Vagrant up works ok but running the full install, the sites do not render: > > http://bedrock.readthedocs.org/en/latest/vagrant.html > > I will try to track down the issue later today. This is not unexpected, > changing vagrant versions often causes compatibility problems. I had to do a few more steps after vagrant up: sudo pico /etc/hosts And then add 127.0.1.1 local.mozilla.org (Note, you'll want this same entry in the /etc/hosts file on your host as well.) Then run a few administrative tasks: cd /vagrant python manage.py compress_assets python manage.py update_product_details And then restart Apache: sudo service apache2 restart Now you should be able to load the following url in your browser: http://local.mozilla.org:8000/en-US/ Most, if not all of that is covered in the other section of the docs, although I'm sure it could be made clearer.
Ah ok you commented out the networking line, we purposefully do not run this on localhost 127.0.1.1 so we would need that back. I think the best thing to do at this stage is submit a pr, it will be easier to make comments and suggest changes there. Prior to submitting the PR these are the things I would ask you to fix: 1. Put back the private networking line 2. Change the host box back to the one I created Based on these changes I only see us needing minor adjustments to the documentation: 1. The vagrant version can be updated to 1.2.5+ 2. We should specify virtualbox needs to be 4.2, vagrant does not support the latest version folks would get in the default download. Please include the documentation changes in the PR.
I went ahead and made these adjustments. Pull request is here: https://github.com/mozilla/bedrock/pull/1648
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/7a4120c29ca0e92db6d2c7bfb3ab321b0e02f659 Fix Bug 943934: Update Vagrant Version, Add MySQL Pre-Req, Update Documentation Removed commented out code. https://github.com/mozilla/bedrock/commit/d028a66ab7f1f77acba7b5990dcda1e5dab58128 Merge pull request #1648 from bensternthal/945870-vagrant-db-update Fix Bug 943934: Update Vagrant Version, Add MySQL Pre-Req, Update Docume...
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.