[
https://issues.apache.org/jira/browse/JCLOUDS-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034703#comment-15034703
]
Ignasi Barrera commented on JCLOUDS-1043:
-----------------------------------------
The problem is in the client id. jclouds parses it to extract the project id
and the regular expression used does not match.
There is an easy workaround, though: just set [the PROJECT_NAME
property|https://github.com/jclouds/jclouds/blob/master/common/googlecloud/src/main/java/org/jclouds/googlecloud/config/GoogleCloudProperties.java#L36]
when creating the context to preconfigure the project id; if the property is
set jclouds won't try to parse the client id to extract the project id.
[This is the code that parses the client id and
fails|https://github.com/jclouds/jclouds/blob/master/common/googlecloud/src/main/java/org/jclouds/googlecloud/config/CurrentProject.java],
in case you cant to try fixing it and send a pull request!
> Google IAM release breaks GoogleComputeEngineHttpApiModule
> ----------------------------------------------------------
>
> Key: JCLOUDS-1043
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1043
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute
> Affects Versions: 1.9.1
> Environment: Google Compute Engine + JClouds
> Reporter: Nelson Araujo
> Priority: Blocker
> Fix For: 1.9.2
>
>
> JClouds relies on parsing the service account email address to extract the
> Project ID from it. With the upgrade of Google Compute Engine to integrate
> with Cloud IAM (https://cloud.google.com/iam) the user is in control of the
> service account name.
> Without the project ID fixed at the beginning of the account email JClouds
> fails to identify the project and all requests fail.
> Problem happens in
> org.jclouds.googlecomputeengine.config.GoogleComputeEngineHttpApiModule:
> @Provides @UserProject Supplier<String> supplyProject()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
