[jira] [Commented] (LIBCLOUD-607) Caching of GCE bearer token results in unexpected errors

["Eric Johnson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LIBCLOUD-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261454#comment-14261454 ] 

Eric Johnson commented on LIBCLOUD-607:
---------------------------------------

Hi Jad,

I'm going to close this out and I believe the issue has been fixed. Please re-open and update if I'm mistaken.

Thanks!
Eric

> Caching of GCE bearer token results in unexpected errors
> --------------------------------------------------------
>
>                 Key: LIBCLOUD-607
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-607
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>    Affects Versions: 0.14.0-beta3
>         Environment: MacOS 10.9.4
>            Reporter: Jad Boutros
>            Assignee: Eric Johnson
>              Labels: Google
>
> ** 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:
> libcloud.common.google.ResourceNotFoundError: {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
(v6.3.4#6332)