[LIBCLOUD-607] Caching of GCE bearer token results in unexpected errors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.14.0-beta3
• Component/s: Compute
• Labels: Google

Environment

MacOS 10.9.4

• Assignee: Eric Johnson
• Reporter: Jad Boutros
• Created: 25/Aug/14 20:46
• Updated: 30/Dec/14 20:18
• Resolved: 30/Dec/14 20:18

Description

• • 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.