search

collective / collective.hostout

zc.buildout deployment and remote control
22 stars 7 forks source link

deploy can't find remote 'zc.buildout' package #33

Open simahawk opened 12 years ago

simahawk commented 12 years ago

Hi, I'm testing c.hostout using the example of the minimal WSGI app (which is working locally). I'm doing this into a dedicated virtualenv.

When I run deploy it fails complaining that """pkg_resources.Requirement.parse('zc.buildout')""" on the remote machine (a virtualbox vm) returns None

Here's the full traceback:

bin/hostout host1 deploy

Hostout: Running command 'deploy' from 'collective.hostout.fabfile' Hostout: Running command 'predeploy' from 'collective.hostout.fabfile' [simahawk@192.168.0.4:22] run: /bin/bash -l -c "PATH=\$PATH:\"/home/simahawk/hostout_demo\" [ -e /home/simahawk/hostout_demo/bin/buildout ]" [simahawk@192.168.0.4:22] Login password: Hostout: Running command 'precommands' from 'collective.hostout.fabfile' Hostout: Running command 'uploadeggs' from 'collective.hostout.fabfile' [simahawk@192.168.0.4:22] run: /bin/bash -l -c "PATH=\$PATH:\"/home/simahawk/hostout_demo\" ls /home/simahawk/buildout-cache/downloads/dist" [simahawk@192.168.0.4:22] out: deploy_LUVN1OSK7xBWNjIHKZXF6g.tgz hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA.zip

Hostout: Preparing eggs for transport Hostout: Develop egg /home/simahawk/dev/hostout/example/src/hellowsgi changed. Releasing with hash 8MiseM54u-pckYopRbj5PA running clean running egg_info writing hellowsgi.egg-info/PKG-INFO writing top-level names to hellowsgi.egg-info/top_level.txt writing dependency_links to hellowsgi.egg-info/dependency_links.txt writing entry points to hellowsgi.egg-info/entry_points.txt reading manifest file 'hellowsgi.egg-info/SOURCES.txt' writing manifest file 'hellowsgi.egg-info/SOURCES.txt' running sdist warning: sdist: standard file not found: should have one of README, README.txt warning: sdist: missing required meta-data: url warning: sdist: missing meta-data: either (author and author_email) or (maintainer and maintainer_email) must be supplied creating hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA creating hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi creating hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info making hard links in hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA... hard linking setup.cfg -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA hard linking setup.py -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA hard linking hellowsgi/init.py -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi hard linking hellowsgi.egg-info/PKG-INFO -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info hard linking hellowsgi.egg-info/SOURCES.txt -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info hard linking hellowsgi.egg-info/dependency_links.txt -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info hard linking hellowsgi.egg-info/entry_points.txt -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info hard linking hellowsgi.egg-info/not-zip-safe -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info hard linking hellowsgi.egg-info/top_level.txt -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info copying setup.cfg -> hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA Writing hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/setup.cfg creating '/tmp/tmpGLKdb3/hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA.zip' and adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA' to it adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/setup.cfg' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/PKG-INFO' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/setup.py' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi/init.py' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/not-zip-safe' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/entry_points.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/top_level.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/PKG-INFO' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/dependency_links.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/SOURCES.txt' creating '/tmp/tmpGLKdb3/hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA.zip' and adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA' to it adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/setup.cfg' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/PKG-INFO' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/setup.py' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi/init.py' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/not-zip-safe' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/entry_points.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/top_level.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/PKG-INFO' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/dependency_links.txt' adding 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA/hellowsgi.egg-info/SOURCES.txt' removing 'hellowsgi-0.0dev-8MiseM54u-pckYopRbj5PA' (and everything under it) Hostout: Eggs to transport: hellowsgi = 0.0dev-8MiseM54u-pckYopRbj5PA [simahawk@192.168.0.4:22] put: /tmp/tmpsioujf -> /home/simahawk/hostout_demo/pinned.cfg Hostout: Running command 'uploadbuildout' from 'collective.hostout.fabfile' [simahawk@192.168.0.4:22] run: /bin/bash -l -c "PATH=\$PATH:\"/home/simahawk/hostout_demo\" test -f /home/simahawk/buildout-cache/downloads/dist/deploy_LUVN1OSK7xBWNjIHKZXF6g.tgz || echo 'None'" [simahawk@192.168.0.4:22] run: /bin/bash -l -c "cd /home/simahawk/hostout_demo && PATH=\$PATH:\"/home/simahawk/hostout_demo\" tar -p -xvf /home/simahawk/buildout-cache/downloads/dist/deploy_LUVN1OSK7xBWNjIHKZXF6g.tgz" [simahawk@192.168.0.4:22] out: base.cfg [simahawk@192.168.0.4:22] out: prod.cfg

Hostout: Running command 'buildout' from 'collective.hostout.fabfile' [simahawk@192.168.0.4:22] put: /tmp/tmpQjdhRM -> /home/simahawk/hostout_demo/host1-LUVN1OSK7xBWNjIHKZXF6g.cfg [simahawk@192.168.0.4:22] run: /bin/bash -l -c "cd /home/simahawk/hostout_demo && PATH=\$PATH:\"/home/simahawk/hostout_demo\" test -e \"\$(echo pinned.cfg)\"" [simahawk@192.168.0.4:22] run: /bin/bash -l -c "cd /home/simahawk/hostout_demo && PATH=\$PATH:\"/home/simahawk/hostout_demo\" bin/buildout -c host1-LUVN1OSK7xBWNjIHKZXF6g.cfg " [simahawk@192.168.0.4:22] out: Traceback (most recent call last): [simahawk@192.168.0.4:22] out: File "bin/buildout", line 17, in [simahawk@192.168.0.4:22] out: import zc.buildout.buildout [simahawk@192.168.0.4:22] out: File "/usr/local/lib/python2.6/dist-packages/zc/buildout/buildout.py", line 39, in [simahawk@192.168.0.4:22] out: import zc.buildout.download [simahawk@192.168.0.4:22] out: File "/usr/local/lib/python2.6/dist-packages/zc/buildout/download.py", line 20, in [simahawk@192.168.0.4:22] out: from zc.buildout.easy_install import realpath [simahawk@192.168.0.4:22] out: File "/usr/local/lib/python2.6/dist-packages/zc/buildout/easy_install.py", line 81, in [simahawk@192.168.0.4:22] out: pkg_resources.Requirement.parse('zc.buildout')).location [simahawk@192.168.0.4:22] out: AttributeError: 'NoneType' object has no attribute 'location'

Fatal error: run() received nonzero return code 1 while executing!

Requested: bin/buildout -c host1-LUVN1OSK7xBWNjIHKZXF6g.cfg Executed: /bin/bash -l -c "cd /home/simahawk/hostout_demo && PATH=\$PATH:\"/home/simahawk/hostout_demo\" bin/buildout -c host1-LUVN1OSK7xBWNjIHKZXF6g.cfg "

None

falkolab commented 12 years ago

same trouble, is there a solution?

domenkozar commented 12 years ago

I've seen this one before, not sure where.

falkolab commented 12 years ago

hostout use old bootstrap.py?

djay commented 12 years ago

yes that could be it. To make host more reliable hostout uses bootstrap.py thats in hostout package. I guess it could look in the same dir as buildout or try and download one. Alternatively it could be changed to install buildout into a virtualenv and run "buildout init". Ideas on which would be the most reliable?