Closed
Bug 1179529
Opened 9 years ago
Closed 9 years ago
Fix the Vagrant environment
Categories
(Tree Management Graveyard :: OrangeFactor, defect, P2)
Tree Management Graveyard
OrangeFactor
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: emorley, Assigned: emorley)
Details
It's currently broken, since the version of pip wasn't pinned & pip has since changed in a backwards incompatible manner.
==> default: notice: /Stage[main]/Init/Exec[update_apt]/returns: executed successfully
==> default: notice: /Stage[main]/Init/Package[python-software-properties]/ensure: ensure changed 'purged' to 'present' ==> default: notice: /Stage[main]/Python/Package[python-wsgi-intercept]/ensure: ensure changed 'purged' to 'present'
==> default: notice: /Stage[main]/Python/Package[python-distribute]/ensure: ensure changed 'purged' to 'present'
==> default: notice: /Stage[main]/Python/Exec[pip-install]/returns: executed successfully
==> default: notice: /Stage[main]/Python/Package[mercurial]/ensure: ensure changed 'purged' to 'present'
==> default: notice: /Stage[main]/Python/Exec[virtualenv-install]/returns: executed successfully
==> default: notice: /Stage[main]/Python/Exec[virtualenv-create]/returns: executed successfully
==> default: notice: /Stage[main]/Python/Package[python2.7-dev]/ensure: ensure changed 'purged' to 'present'
==> default: err: /Stage[main]/Python/File[/home/vagrant/project/puppet/cache/pip]/ensure: change from absent to directory failed: Cannot create /home/vagrant/project/puppet/cache/pip; parent directory /home/vagrant/project/puppet/cache does not exist
==> default: err: /Stage[main]/Python/Exec[pip-cache-ownership]/returns: change from notrun to 0 failed: /bin/chown -R vagrant:vagrant /home/vagrant/project/puppet/cache/pip && /bin/chmod ug+rw -R /home/vagrant/project/puppet/cache/pip returned 1 instead of one of [0] at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/classes/python.pp:78
Assignee | ||
Comment 1•9 years ago
|
||
Even after fixing that, I now get:
[Thu Jul 02 00:15:39 2015] [error] [client 33.33.33.1] mod_wsgi (pid=10077): Target WSGI script '/home/vagrant/project/server/woo_server.py' does not contain WSGI application 'application'.
The version of web.py we're using is unpinned, however it doesn't appear to have been updated since the Vagrant project was created (https://github.com/webpy/webpy/blob/master/ChangeLog.txt), so not sure why that's broken.
Adding this to woo_server.py fixes that problem:
```
if __name__ == '__main__':
...
else:
application = app.wsgifunc()
```
However I then get a "not found" when navigating to http://orangefactor/
:-/
Will take another look tomorrow. Unfortunately this is what we get when versions are not pinned (both in the pip requirements file and in the puppet config) booooooooooooooooooooo.
Assignee | ||
Comment 2•9 years ago
|
||
I have fixed the provision step locally, but mod_wsgi still isn't correctly set up. Not sure if this ever worked, or if it did, a package version must have changed somewhere.
Either way, I don't really see the value in this Vagrant project - with the updated readme (as of bug 1179991), it's possible to test locally without a VM, even on Windows.
IMO we should just delete the Vagrant project outright.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•4 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•