Closed
Bug 919270
Opened 11 years ago
Closed 10 years ago
Fix up Vagrant for balrog
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
Details
(Whiteboard: [balrog])
Attachments
(1 file)
4.62 KB,
patch
|
bhearsum
:
review+
nthomas
:
checked-in+
|
Details | Diff | Splinter Review |
Strongly suspect https://github.com/mozilla/balrog/commit/b26421f4f7594c728b5fcf2c96744a294aa17f5f will have broken it.
Assignee | ||
Comment 1•11 years ago
|
||
Also, at some point I upgraded to Vagrant 1.2.4 (older version unknown) and now get this: There were warnings and/or errors while loading your Vagrantfile. Your Vagrantfile was written for an earlier version of Vagrant, and while Vagrant does the best it can to remain backwards compatible, there are some cases where things have changed significantly enough to warrant a message. These messages are shown below. Warnings: * The 'v-root' shared folders have been renamed to 'vagrant-root'. Assuming you meant 'vagrant-root'... ----- It's a simple fix: diff --git a/Vagrantfile b/Vagrantfile index e1cf1c3..c32ab11 100644 --- a/Vagrantfile +++ b/Vagrantfile @@ -12 +12 @@ Vagrant::Config.run do |config| - config.vm.share_folder("v-root", MOUNT_POINT, ".") + config.vm.share_folder("vagrant-root", MOUNT_POINT, ".")
Updated•11 years ago
|
Component: Tools → Balrog: Backend
QA Contact: hwine → bhearsum
Assignee | ||
Comment 3•10 years ago
|
||
Torched my vagrant vm the other day, have a patch in hand from setting up a new one.
Assignee: nobody → nthomas
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•10 years ago
|
||
This WFM with Vagrant 1.5.2 on Mac 10.9.2 (both current latest), with VirtualBox 4.2.6 (which is stale). * fixes reference to deprecated v-root config variable * adds balrog.ini to .gitignore, since the ini files live in code dir now * apache changes * log to dirs matching domains used elsewhere * rotate logs every 24 hours, rather than every hour * serve jss/css/images using Apache to avoid respawning a wsgi for each * update templates for the two ini files, and put them next to source instead of /etc/aus. Moves any file already present to <foo>.puppet-backup
Attachment #8402459 -
Flags: review?(bhearsum)
Comment 5•10 years ago
|
||
Comment on attachment 8402459 [details] [diff] [review] Assorted fixes Review of attachment 8402459 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me!
Attachment #8402459 -
Flags: review?(bhearsum) → review+
Comment 6•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog https://github.com/mozilla/balrog/commit/18c9b71ea4ab530000f8295969e68951e2f91533 Bug 919270, update Vagrant config for code changes, r=bhearsum
Assignee | ||
Comment 7•10 years ago
|
||
Comment on attachment 8402459 [details] [diff] [review] Assorted fixes https://github.com/mozilla/balrog/commit/18c9b71ea4ab530000f8295969e68951e2f91533
Attachment #8402459 -
Flags: checked-in+
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog https://github.com/mozilla/balrog/commit/37ec9bd9f3e991c9758b5bd7c68df99dd0e527b5 Bug 919270, followup fix for cef logging
Assignee | ||
Comment 9•10 years ago
|
||
The followup ensures /var/log/auscef.log is writeable by Apache.
Updated•4 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•