Skip to content
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

Pipelines no longer working in dev server after updating to latest cloud sdk #103

Open
snstanton opened this issue Sep 18, 2016 · 9 comments

Comments

@snstanton
Copy link

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 126:

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. Note that the pipeline is not running in the default service. Also, 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?

@snstanton snstanton changed the title Pipelines no longer working after updating to latest cloud sdk Pipelines no longer working in dev server after updating to latest cloud sdk Sep 18, 2016
@Erfa Erfa mentioned this issue Oct 5, 2016
@Erfa
Copy link

Erfa commented Oct 5, 2016

I have the exact same problem, with the original App Engine SDK. I created a small repo that shows the problem: https://github.com/Erfa/mapreduce-test

@javpaw
Copy link

javpaw commented Oct 14, 2016

I'm having the same problem, It's not working on my dev server.

@brunoripa
Copy link

Same for me. Also, i have been suggested to downgrade to 122.0.0, but the issue is still there.

@timmehmainframe
Copy link

This is fixed by: GoogleCloudPlatform/appengine-pipelines@2f1930b

@georgewhewell
Copy link

above 'fix' didn't work for me- I added to my app.yaml:

module: default
version: someversion

and it started working. there has not been new release on pypi since that commit, so presumably this is broken out of the box for anyone with updated sdk.

@psundar
Copy link

psundar commented Dec 7, 2016

The fix mentioned by @timmehmainframe worked. I commented the two lines mentioned below under src/pipeline/util.py:
if module == "default":
return version
Thank you.

@bjohnson-va
Copy link

For me, specifically, the fix was to add:

module: default
version: default

to app.yaml.

The version had to be default. I'm not going to pretend I understand why.

@magoarcano
Copy link

I only added to the app.yaml:
version: default
And it works. But app engine documentation at https://cloud.google.com/appengine/docs/standard/python/config/appref#version says:

The version ID can contain lowercase letters, digits, and hyphens. It cannot begin with the prefix ah- and the names default and latest are reserved and cannot be used.

@diogovk
Copy link

diogovk commented Apr 11, 2017

Indeed this is happening, and changing version to default works. (GoogleAppEnginePipeline version 1.9.22.1)

What would a definite solution to this problem would look like so I can make a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants