-
Notifications
You must be signed in to change notification settings - Fork 60
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
cloud sdk 123 causes PipelineSetupError in dev server #72
Comments
I believe I have a similar error:
Ideas? |
I was able to fix that by modifying util.py:53 to: |
@rtshadow could you please make that a pull request? |
Per @rtshadow's comment on GoogleCloudPlatform#72, enable TEST_MODE when in dev_appserver to avoid an otherwise confusing and fatal error later.
I have a mapreduce pipeline that worked in SDK 122 that now fails in the dev server with the following error after updating to SDK 123:
Traceback (most recent call last):
File "/vl/local/google-cloud-sdk/platform/google_appengine/lib/webapp2-2.5.2/webapp2.py", line 570, in dispatch
return method(_args, *_kwargs)
File "/Users/stanton/src/vlshare/appserver/src/vl/base.py", line 645, in wrapper
return handler(_args, *kwargs)
File "/Users/stanton/src/vlshare/appserver/src/vlops/handlers.py", line 319, in any
result = func(self.request)
File "/Users/stanton/src/vlshare/appserver/src/vlops/admin/files.py", line 301, in getZone
result = launchPipeline(GetZonePipeline(zone.key.urlsafe()))
File "/Users/stanton/src/vlshare/appserver/src/vl/pipe_utils.py", line 62, in launchPipeline
pipeline.start(base_path='/ops/pipeline')
File "/Users/stanton/src/vlshare/appserver/src/lib/pipeline/pipeline.py", line 673, in start
self, idempotence_key, str(e)))
PipelineSetupError: Error starting vlops.admin.files.GetZonePipeline(('aghkZXZ-Tm9uZXIXCxIKWm9uZUVudGl0eRiAgICAgMCvCgyiAQZnbG9iYWw',), *{})#342c4ceab7084adfb389b35b45960fdd:
As far as I can tell the pipeline is having problems submitting tasks to the task queue. Everything works as expected in the production environment, so this is specifically a problem with the dev server.
Any ideas? What additional logging would be helpful here?
The text was updated successfully, but these errors were encountered: