libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Johnson (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-607) Caching of GCE bearer token results in unexpected errors
Date Fri, 03 Oct 2014 14:22:33 GMT


Eric Johnson commented on LIBCLOUD-607:

Hi Jad,

Thanks for flagging this.  I understand you have a temporary workaround until a fix can be
added.  I'm curious if you've seen this thread[1] and if you think this would be a suitable
solution.  If so, I can suggest they turn it into a pull-request, or work on an alternate


> Caching of GCE bearer token results in unexpected errors
> --------------------------------------------------------
>                 Key: LIBCLOUD-607
>                 URL:
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.14.0-beta3
>         Environment: MacOS 10.9.4
>            Reporter: Jad Boutros
> ** Affected release version is 0.15.1 but I can't type it in the version list. **
> Can't use libcloud to access more than one project on Google Compute Engine. 
> The not very helpful errror message is:
> {u'domain': u'global', u'message': u"The
resource 'projects/xxx' was not found", u'reason': u'notFound'}
> Captured debug log via  LIBCLOUD_DEBUG and noticed that for the second project, it was
still accessing via the first project's bearer token. Looks like this gets cached in ~/.gce_libcloud_auth
> Then found some search results on the web suggesting this file needs to be deleted but
that sounds pretty clunky considering that I want to navigate multiple GCE projects in one
execution run of the program.

This message was sent by Atlassian JIRA

View raw message