Google cloud credential error

[moonwalker]

Hello,

I’ve been trying to connect a google cloud account to deadline 8.0.0.67 for a few hours (first time).
I was thinking that it was a configuration issue, but I saw this error in the monitor log and began to think it could be a bug ?!

I managed to have the “The authentication flow has completed.” (localhost:8088/?code=4/…#), but no file is proposed to download, and I have a popup in the monitor :

Here is the monitor log :

PYTHON: Your browser has been opened to visit:
PYTHON: accounts.google.com/o/oauth2/au … id=(….apps.googleusercontent.com&access_type=offline
PYTHON: If your browser is on a different machine then exit and re-run this
PYTHON: application with the command-line parameter
PYTHON: --noauth_local_webserver
Traceback (most recent call last):
File “/u/deadlinerepo8beta/cloud/Google/Google.py”, line 99, in RefreshConnection
credentials = run_flow(flow, storage, flags)
File “/u/pedeutsch/.local/lib/python2.7/site-packages/oauth2client/util.py”, line 142, in positional_wrapper
return wrapped(*args, **kwargs)
File “/u/pedeutsch/.local/lib/python2.7/site-packages/oauth2client/tools.py”, line 235, in run_flow
storage.put(credential)
File “/u/pedeutsch/.local/lib/python2.7/site-packages/oauth2client/client.py”, line 403, in put
self.locked_put(credentials)
File “/u/pedeutsch/.local/lib/python2.7/site-packages/oauth2client/file.py”, line 110, in locked_put
self._create_file_if_needed()
File “/u/pedeutsch/.local/lib/python2.7/site-packages/oauth2client/file.py”, line 97, in _create_file_if_needed
open(self._filename, ‘a+b’).close()
IOError: [Errno 2] No such file or directory: u’’

What do you think ?

Cheers,
Pierre

[Coulter]

Hi Pierre,

You need to specify the location of the oath.dat file in advance (second option from the top). Then it will be created in that location when you verify access. That said, we should have a better error message if the user has not specified where the .dat file is to be saved when clicking Verify Access.

[Coulter]

Follow-up: I’ve confirmed there are some problems with the Verify Access procedure. I’ve logged an internal issue to have this reviewed. Thanks for reporting this issue.

You should be able to get it working, though, if you supply the intended destination of the oauth.dat file.

[moonwalker]

Oh, got it

I’ll let you know if anything else comes up.

Pierre